On Sat, Nov 02, 2002, Dan Streetman <[EMAIL PROTECTED]> wrote:
> On Sat, 2 Nov 2002, Johannes Erdfelt wrote:
>
> >Is the USB get configuration control message (section 9.4.2) and get
> >interface control message (section 9.4.4) not good enough?
>
> aha! I never read those close enough, always as
On Sat, 2 Nov 2002, Johannes Erdfelt wrote:
>Is the USB get configuration control message (section 9.4.2) and get
>interface control message (section 9.4.4) not good enough?
aha! I never read those close enough, always assumed they got the
descriptors. there is a slight problem with the get_i
On Wed, Oct 30, 2002, Dan Streetman <[EMAIL PROTECTED]> wrote:
> This patch adds ioctls to get the active config# and interface setting#
> through usbfs.
>
> As far as I can tell, the only way to currently get the active config is
> via the devices file (generates bus traffic, I'd rather not u
David, any opinions on this patch?
David?
Sorry -- I had no problems with it, as I recall,
that's why I didn't comment ... :)
- Dave
---
This sf.net email is sponsored by: See the NEW Palm
Tungsten T handheld. Power & Color in a compa
> Why? What is that needed for? Oh wait, you don't have a pci device,
> right?
Correct.
>So where in the device tree does the sa111 controller show up?
>What type of bus is it on?
rmk and pat worked this out:
/sys/bus/system/devices/SA0
/sys/bus/RAB/devices/0400
Hi,
This is a tiny patch to 2.5.45. usb-midi requires SOUND,
otherwise, when built in-kernel but soundcore is modular,
usb-midi can't resolve some sound interfaces, like so:
ld -m elf_i386 -e stext -T arch/i386/vmlinux.lds.s
arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/buil
I implemented a Cypress SL811HS Host Controller into
linux-2.4.18-rmk7 for a custom board based on SA1110.
I have enabled Keyboard and Mouse and iPaq USB support
I have attached an USB keyboard
I have the following messages from my linux box.
My questions are:
1) -- At the end I see some errors,
On Friday 01 November 2002 08:47, Alan Stern wrote:
> ...I don't see anything wrong with them, which makes it
> sound like there's some sort of firmware problem with the drive. On the
> other hand, it could just be something funny going on with that particular
> drive that I don't know about -- bu
