On Wednesday 24 November 2004 13:01, Fabio Coatti wrote:
>
> Ok, it seems that now the device is detected without problems at first try;
> I've tried several times with this setup in modprobe.conf:
> options usbcore old_scheme_first=1
> and I'm unable to reproduce the behaviour of missed detectio
Hello
I guess, it is not a USB problem, really, it just appeared with USB. On a
2-way running 2.6.9 the onboard UHCI device is configured to IRQ 9 via
XT-PIC???
CPU0 CPU1
0: 588054123IO-APIC-edge timer
1:360 0IO-APIC-edge i8042
On Tue, Nov 23, 2004 at 11:18:34AM -0800, David Brownell wrote:
> The UDC in Intel's "Bulverde" processors is incompatible with the
> one in their PXA 25x/26x/21x processors, and has different sorts
> of restrictions. For example, it can implement real CDC Ethernet,
> while the earlier (PXA 25x et
On Wednesday 24 November 2004 13:25, Alan Stern wrote:
> On Wed, 24 Nov 2004, David Brownell wrote:
>
> > On Tuesday 23 November 2004 14:15, Alan Stern wrote:
> > > It's not a question of using timers or anything else. If wakeup_enabled
> > > isn't set then the HCD _must not_ allow wakeup/resume
Alle 03:16, mercoledì 24 novembre 2004, David Brownell ha scritto:
> OK, so there may be two different problems then. The one
> producing the stack backtraces from SCSI/kobject stuff;
> and a change in behavior related to USB.
>
> What happens if you set the "old_scheme_first" usbcore
> parameter
On Wed, 24 Nov 2004, Sara Fonseca wrote:
> I managed to build and load the drivers, but how do I start testing
> read and write operations for example?
Just do reads and writes to the device corresponding to your gadget. For
instance, if the gadget shows up as /dev/sda, then do reads and writes
On Wed, 24 Nov 2004, David Brownell wrote:
> On Tuesday 23 November 2004 14:15, Alan Stern wrote:
> > It's not a question of using timers or anything else. If wakeup_enabled
> > isn't set then the HCD _must not_ allow wakeup/resume signalling in any
> > form. Regardless of whether it is able to.
Hello,
I've just bought a Dane-Elec zMage Compact Flash Reader/Writer. FWIW, it has
a "Certified Hi-Speed USB" sticker on the box, and underneath the sticker it
says "USB 2.0 compatible".
The problem is that with ehci-hcd it fails:
Kernel 2.6.9:
dmesg> usb 1-3: new high speed USB device using
Новая коллекция пледов из 100% новозеландской шерсти от www.elitpresent.ru.
Новые расцветки, новые подарки!
the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
I managed to build and load the drivers, but how do I start testing
read and write operations for example?
On Mon, 22 Nov 2004 10:33:39 -0500 (EST), Alan Stern
<[EMAIL PROTECTED]> wrote:
> On Mon, 22 Nov 2004, Sara Fonseca wrote:
>
> > ok Alan, thanks...
> > but how do I change the USB Gadget co
On Tuesday 23 November 2004 20:03, ëíì wrote:
> Hello.
> In driver/usb/gadget, there are many gadget drivers supporting NetChip.
Right, but those same gadget drivers support several other
peripheral controllers. Like ones from TI (omap_udc),
Intel (pxa2xx_udc), Toshiba (goku_udc), and more ...
On Wed, Nov 24, 2004 at 10:57:18AM +0100, Luca Risolia wrote:
> PWLIB/Gnomemeeting CVS already supports BGGR8, I wrote a patch for XawTV
> sometime ago, and someone is attempting to develop a low-level "libv4l2"
> library including vendor-specific decoders (where cpu-optimizations would
> be poss
On Tuesday 23 November 2004 14:15, Alan Stern wrote:
> It's not a question of using timers or anything else. If wakeup_enabled
> isn't set then the HCD _must not_ allow wakeup/resume signalling in any
> form. Regardless of whether it is able to. That's the whole point of the
> wakeup_enabled fla
On Wednesday 24 November 2004 08:03, Alan Stern wrote:
> On Tue, 23 Nov 2004, David Brownell wrote:
>
> > > I would be happy to make it not be special by allowing any device to be in
> > > USB_STATE_SUSPENDED, even when CONFIG_USB_SUSPEND is not set. The
> > > difference being that when CONFIG_US
Many of the issues raised here were concerned with how to handle the case
of CONFIG_USB_SUSPENDED not set. Given the strategy of maintaining the
drivers' current behavior for that case, there's not much point in
worrying about it any more. But one or two aspects may still be of
interest...
On Wednesday 24 November 2004 05:12, [EMAIL PROTECTED] wrote:
>
> Hi!
>
> Im going to have a DSP-BF533(blackfin) ported on my USB2.0. Can i find
> drivers
> for this usb-DSP anywhere? This DSP is going to compile some of the thing my
> CPU think its hard to do. Or can i find drivers for any us
On Wednesday 24 November 2004 01:57, Luca Risolia wrote:
> On Wed, Nov 24, 2004 at 08:12:10AM +0100, Vojtech Pavlik wrote:
>
> > Btw, how do you suggest handling the fact that the image is rotated 180
> > degrees as sent directly by the cam?
>
> I would probably play with some FX2 registers to fi
Hi!
Im going to have a DSP-BF533(blackfin) ported on my USB2.0. Can i find drivers
for this usb-DSP anywhere? This DSP is going to compile some of the thing my
CPU think its hard to do. Or can i find drivers for any usb-dsp somewhere?
-
This m
yes
but this occurs on two different computers... (??)
also... if the phone is plugged in and when the computer powers up
it then recognizes the device as acm type...
but if i hotplug in after system is up and running (or unplug then
plug it in... then the below error occurs)
i was not s
On Wed, Nov 24, 2004 at 08:12:10AM +0100, Vojtech Pavlik wrote:
> On Wed, Nov 24, 2004 at 03:40:14AM +0100, Luca Risolia wrote:
>
> > > The fact that the camera contains an OmniVision sensor and the fact that
> > > it uses the ovcamchip module don't imply that the camera can do YUV in
> > > hardwa
20 matches
Mail list logo