[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#333858: Proposed improved patch for yaird



On Sun, Oct 16, 2005 at 10:10:05PM +0200, Erik van Konijnenburg wrote:
> On Sun, Oct 16, 2005 at 09:40:13PM +0200, Sven Luther wrote:
> > BTW, i wonder how yaird behaves with regard to /etc/mkinitrd/modules, or if
> > there is some altrenative way of handling modules. I have a case where the
> > ehci module should be loaded before the ohci/uhci ones, and i don't know how
> > to make that happen. I used to have them in the right order in
> > /etc/mkinitrd/modules, so i wonder if this is also the right thing to do here.
> > I had fixed initrd-tools to include both. What does yaird do on this topic ? 
> 
> Yaird ignores /etc/mkinitrd/modules.  Instead, use a MODULE line
> in /etc/yaird/Default.cfg.  (this used to be /usr/lib/yaird/conf/Default.cfg
> in 0.0.11-3).  The MODULE line honours module dependencies, module options,
> blacklisting, most of what you would expect.

Cool, ...

> Are you working around buggy hardware here, or is this an aspect of
> the USB definition that yaird does not know enough about?  If the latter,
> I'll need to  look into making it happen automatically.

Well, we indeed had an older buggy firmware on the pegasos, which had some
interrupt problem when there was an USB 2 interrupt coming in, being read by
the uhci/ohci driver while ehci was not loaded or something, but it is fixed
now. I am no expert on this, but the usb guy is telling me that the ehci
driver should be the first one to scan the ports and that the other wait that
it finishes, because uhci/ohci drivers can drive cards in usb 1.1 mode even if
they are usb 2.0 cards, and they don't know how to give the device back to the
ehci/usb 2.0 driver if it is loaded afterward.

I am not sure i fully understand the details of this, nor if this is a kernel
bug in the usb subsystem or something, but well, in doubt, if we can always
load ehci before uhci/ohci if we have a usb 2.0 card, then we should do it,
and this applies to yaird with usb 2.0 connected keyboards, i think.

> Oh, and a BTW in return: I can't seem to find the yaird SVN on Alioth
> you mentioned.  Is there an url that an unregisted user can use to access it?

It is part of the kernel SVN right now :

  svn+ssh://<user>@svn.debian.org/svn/kernel/dists/trunk/utils/yaird
  svn://svn.debian.org/svn/kernel/dists/trunk/utils/yaird

first one for alioth member, second anonymous checkout, but Jonas told me he
wanted to do it right and setup it by himself, so i guess he will have to
reply to you about this.

also, for write access, you need to have an alioth account and being added to
the project, obviously.

Friendly,

Sven Luther



Reply to: