On Sunday 30 July 2006 8:58 pm, Greg KH wrote:
> On Sun, Jul 30, 2006 at 08:51:17PM -0700, David Brownell wrote:
> > This must only have been build tested on sa-1100 hardware,
> > but the chip is also used on some pxa-25x boards.
>
> Is this 2.6.18 material, or can it wait?
It can wait ... it's b
Hey,
Trying to modify the Micronas GO7007SB Driver to work with the board
that I've got. I've managed to get the video working, but now I'd like
to get the audio working. So far, all the other boards that the driver
has been written to work with either do not support audio or support
both vide
On Sun, Jul 30, 2006 at 08:51:17PM -0700, David Brownell wrote:
> This must only have been build tested on sa-1100 hardware,
> but the chip is also used on some pxa-25x boards.
Is this 2.6.18 material, or can it wait?
thanks,
greg k-h
This must only have been build tested on sa-1100 hardware,
but the chip is also used on some pxa-25x boards.
- Dave
Build fixes for ohci-sa with PXA ... it assumes SA-1100 CPUs,
but some PXA 255 boards use it too. (And minor whitespace fixes.)
Signed-off-by: David Brownell <[EMAIL PROTECTED
On Sun, Jul 30, 2006 at 10:54:38PM -0400, Dmitry Torokhov wrote:
> Hi,
>
> Currently we have 2 main places for input-related devices in *config -
> one under "Input device support" and another under "USB support".
> While the split made perfect sense when USB was somewhat rare and
> did not share
On Sun, 30 Jul 2006 22:54:38 -0400, Dmitry Torokhov <[EMAIL PROTECTED]> wrote:
> Currently we have 2 main places for input-related devices in *config -
> one under "Input device support" and another under "USB support".
>[...]
> Do you think it is time to move everything in one place?
I do not a
> > > Are you asking why the method is per-bus? I don't know; the current
> > > implementation doesn't use this feature.
> >
> > At least sl811-hcd could use it, and in general the dma issues need
> > to be tied to the underlying usb_bus not a usb_device since that's how
> > the operations work
Hi,
Currently we have 2 main places for input-related devices in *config -
one under "Input device support" and another under "USB support".
While the split made perfect sense when USB was somewhat rare and
did not share the same infrastructure as the other input device it
does not make sence now
On Sunday 30 July 2006 15:26, Daniel Ritz wrote:
> On Sunday 30 July 2006 20.48, Alan Stern wrote:
> > On Sun, 30 Jul 2006, Daniel Ritz wrote:
> >
> > > there was a report from a user who saw a series of disconnect/connect
> > > until X11 was started up. and of course most of the time the device
>
If USB=m, USB_GADGET=y, the option USB_GADGET_DUMMY_HCD mustn't be
offered since selecting it results in a compile error.
This patch fixes kernel Bugzilla #6534 reported by Toralf Förster.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
--- linux-2.6.18-rc2-mm1-full/drivers/usb/gadget/Kconfig.ol
2006/7/30, Alan Stern <[EMAIL PROTECTED]>:
First, thank you very much for your reply! I got WLAN adapter running
now! (more or less, but it has been recognized as interface wlan0) :)
> Not having an exact duplicate of your hardware, I can't answer that
> question. In fact, you're in a better pos
On Sunday 30 July 2006 20.48, Alan Stern wrote:
> On Sun, 30 Jul 2006, Daniel Ritz wrote:
>
> > there was a report from a user who saw a series of disconnect/connect
> > until X11 was started up. and of course most of the time the device
> > was disconnected when X11 fired up. the workaround he fo
On Sun, 30 Jul 2006, Daniel Ritz wrote:
> there was a report from a user who saw a series of disconnect/connect
> until X11 was started up. and of course most of the time the device
> was disconnected when X11 fired up. the workaround he found was doing
> cat /dev/input/event3 > /dev/null 2>
On Sun, 30 Jul 2006, David Brownell wrote:
> > It's documented in usb.c:usb_buffer_alloc. Obviously the idea is to map a
> > frequently-used DMA buffer just once instead of over and over.
>
> Erm, no ... buffer allocation and buffer mapping are distinct operations,
> that one only affects alloca
On Sun, 30 Jul 2006, niam.tni wrote:
> Hi,
>
> I'm using Kernel 2.6.16 on PDA.
> It has an USB-slot/internal hub where I connect my WLAN adapter to.
> But kernel doesn't configure this adapter "usb 1-2: no configuration
> chosen from 1 choice".
>
> There is a post from Alan Stern
> http://www.ma
On Sun, 30 Jul 2006 11:00:59 -0300, Thiago Galesi <[EMAIL PROTECTED]> wrote:
> 2nd try, addressing the comments
Looks much better now, but how did this happen:
> -static void pl2303_set_termios (struct usb_serial_port *port, struct termios
> *old_termios)
> +static void pl2303_set_termios (stru
2006/7/30, David Brownell <[EMAIL PROTECTED]>:
>
> An external hub would certainly be a good idea, although there's
> also the possibility that the PDA _could_ source 500 mA for a short
> while before its battery gets drained.
That sound's good and that is what I want to do. Then one AC adapter
sh
On Sunday 30 July 2006 8:28 am, niam.tni wrote:
>
> I'm using Kernel 2.6.16 on PDA.
> ...
> "usb 1-2: new config #1 exceeds power limit by 350mA".
>
> I guess, PDA's usb port doesn't supply more than 150mA.
>
> Am I right? Do I really need an external powered usb hub to get WLAN
> adapter (500mA
On Wednesday 26 July 2006 4:59 am, Manish RATHI wrote:
> Hi,
> I've to develop driver for mentor graphics usb controller.
Which one? There are several, with variants.
> It's available on sourceforge.net but no documentation is there.
Got URL? I know that Mentor's code for the HDRC is basical
On Saturday 29 July 2006 1:37 pm, Alan Stern wrote:
> On Fri, 28 Jul 2006, Pete Zaitcev wrote:
>
> > Why do we even have this bus operation method?
>
> It's documented in usb.c:usb_buffer_alloc. Obviously the idea is to map a
> frequently-used DMA buffer just once instead of over and over.
Erm,
Hi,
I'm using Kernel 2.6.16 on PDA.
It has an USB-slot/internal hub where I connect my WLAN adapter to.
But kernel doesn't configure this adapter "usb 1-2: no configuration
chosen from 1 choice".
There is a post from Alan Stern
http://www.mail-archive.com/linux-usb-devel@lists.sourceforge.net/msg
2nd try, addressing the comments
Fixes several lines that overrun 80 columns in Prolific pl2303 driver
Signed-off-by: Thiago Galesi <[EMAIL PROTECTED]>
Index: linux-2.6.17/drivers/usb/serial/pl2303.c
===
--- linux-2.6.17.orig/driver
On Sunday 30 July 2006 03.34, Dmitry Torokhov wrote:
> Hi Daniel,
>
> On Saturday 29 July 2006 18:38, Daniel Ritz wrote:
>
> > - always do usb_submit_urb(dev->irq) in probe() to work around issues
> > with some eGalaxe contollers
>
> Could you elaborate on the issues you are seeing? Submitting U
On Thu, 27 Jul 2006 15:21:37 -0700, Benjamin Cherian <[EMAIL PROTECTED]> wrote:
> On Monday 24 July 2006 23:07, Pete Zaitcev wrote:
> > Anyway, please test the attached patch. Does it do what you want?
>
> Sorry to say that it doesnt. When calling usb_get_string_simple in libusb,
> the program se
24 matches
Mail list logo
