On 27 Oct 2004 at 16h10, David Brownell wrote:
Hi,
> The "message.c" part is fine, but the usbfs/devio change
> only tests one of several paths for device access. (My
> first whack at this only covered a different one!) Can
> you verify this one instead?
I'll do; I'll get back to you next wee
Hi David,
>> Does anybody know if there is any implementation of
>> USB Gadget API controller driver for EZ-USB FX2 chip?
>It's right here with my port of uCLinux to the 8051 ... ;)
Hmmthat's not exactly what I'm thinking off ... :)
>More seriously, I think the "SX2" would be a realistic go
On Wednesday 27 October 2004 18:48, Santoso, Yusdi wrote:
> Hi all,
>
> Does anybody know if there is any implementation of
> USB Gadget API controller driver for EZ-USB FX2 chip?
It's right here with my port of uCLinux to the 8051 ... ;)
More seriously, I think the "SX2" would be a realistic g
On Monday 25 October 2004 11:59, xemc wrote:
>
> It seems these are the main users of DMA. However, DMA seems to be
> referenced in a bunch of other places.
>
> What is td->td_dma used for? How can I get rid of it?
> The same questions go for ed->dma, dma_sync_single_for_device,
> dma_to_td. I
Hi all,
Does anybody know if there is any implementation of USB Gadget API controller driver
for EZ-USB FX2 chip?
Thanks,
Yusdi
---
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reade
David Brownell wrote:
> ... except when CONFIG_PM! Better to just move it
> into "ohci-hub.c" where there's another block of
> forward declarations guarded by CONFIG_PM.
Not sure about this, I haven't looked at the code, but If the forward
declaration was in ohci-hcd.c is because it's probably cal
On Wednesday 27 October 2004 16:59, Stephen Hemminger wrote:
> >
> > ... except when CONFIG_PM! Better to just move it
> > into "ohci-hub.c" where there's another block of
> > forward declarations guarded by CONFIG_PM.
>
> Okay, by the way why have a source layout with multiple .c
> files all in
On Wed, 27 Oct 2004 16:22:30 -0700
David Brownell <[EMAIL PROTECTED]> wrote:
> On Wednesday 27 October 2004 11:04, Stephen Hemminger wrote:
> > With 2.6.10 getting warning about ohci_restart() defined and not used
> > if !CONFIG_PM. Safe to just get rid of the declaration.
>
> ... except when CO
On Wednesday 27 October 2004 02:07, Colin Leroy wrote:
> On 26 Oct 2004 at 09h10, David Brownell wrote:
>
> > What's wrong there is emitting voluminous diagnostics for
> > something that's not an error ... the root hub is suspended,
> > and as with any suspended device, you can't talk to it.
>
>
On Wednesday 27 October 2004 00:19, Colin Leroy wrote:
> On 26 Oct 2004 at 09h10, David Brownell wrote:
>
> Hi,
>
> > What's wrong there is emitting voluminous diagnostics for
> > something that's not an error ... the root hub is suspended,
> > and as with any suspended device, you can't talk to
On Wednesday 27 October 2004 11:04, Stephen Hemminger wrote:
> With 2.6.10 getting warning about ohci_restart() defined and not used
> if !CONFIG_PM. Safe to just get rid of the declaration.
... except when CONFIG_PM! Better to just move it
into "ohci-hub.c" where there's another block of
forwar
On Wednesday 27 October 2004 02:54, Ben Dooks wrote:
> On Tue, Oct 19, 2004 at 03:33:52PM -0700, David Brownell wrote:
> > On Tuesday 19 October 2004 2:14 pm, Ben Dooks wrote:
> > > > If you're up for it, I'd rather see a generic hook for
> > > > turning port N power on/off ... just hang a method i
On Thu, Oct 28, 2004 at 12:18:16AM +0200, Oliver Neukum wrote:
> > if I claim the interface with usb_driver_claim_interface, will usbfs
> > respect it? ?There are only a handful of userspace drivers for this
> > device out there.. and I'm pretty sure they're not active during the
> > test.
>
> Con
Am Mittwoch, 27. Oktober 2004 23:29 schrieb Geoff Oakham:
> if I claim the interface with usb_driver_claim_interface, will usbfs
> respect it? There are only a handful of userspace drivers for this
> device out there.. and I'm pretty sure they're not active during the
> test.
Concerning your cla
On Wednesday 27 October 2004 08:02 am, Mariusz Woloszyn wrote:
> As I wrote before it's a known issue.
> Your camera requires some extra USB cleanup on exit. It has nothing with
> PTP but with USB. You should use usbsoop or something similar to see the
> stransmision under windows drivers.
To reca
On Wed, Oct 27, 2004 at 04:59:17PM -0400, Alan Stern wrote:
> Ah, but other programs may be accessing your device through usbfs without
> your knowledge, without using your driver, and without being stopped by
> your semaphore! For example, any time you do "cat /proc/bus/usb/devices"
> the cat
On Wed, 27 Oct 2004, Geoff Oakham wrote:
> > Have you eliminated the possibility of other programs running in the
> > background also trying to communicate with your device (some Gnome/hotplug
> > programs do that)?
>
> Yes: I have a single semaphore guarding my data structure and access to
> the
Hello,
I am porting the Philips ISP116x driver to a PowerPC 8xx (852T in
particular) board. It is built into the kernel at the moment (i.e. it isn't
a loadable module) and comes up fine and gets and handles interrupts (at
least 2400 of them) while the rest of the kernel is initializing.
Just befo
On Wed, Oct 27, 2004 at 03:49:43PM -0400, Alan Stern wrote:
> > Since the linux-usb implementation is 100% bug-free, my code is the
> > bug's likely home. Should I be holding any locks when I call
> > usb_control_msg() or usb_bulk_msg()?
>
> You certainly shouldn't hold any spinlocks, since those
On Mon, Oct 25, 2004 at 10:40:55AM -0400, Alan Stern wrote:
> On Fri, 22 Oct 2004, Ray Lehtiniemi wrote:
> >
> > so, aside from leftover scsi threads, things seem to be working pretty
> > well now.
>
> I think this patch will solve those problems:
>
> http://marc.theaimsgroup.com/?l=linux-scsi&m
On Tue, 26 Oct 2004, Geoff Oakham wrote:
> Hey Alan,
>
> Unfortunately I haven't had any luck fixing this timing issue, so I've
> returned to seek wisdom and guidance. I've tried:
>
> -capping the average transfer speed in my driver
> -looking for similar behaviour in the Windows dr
Greg:
This patch fixes a tiny SMP-type hole in root-hub synchronization.
Although the HCD glue layer properly unlinks root-hub status URBs
synchronously, it doesn't do so for URBs sent to endpoint 0. This patch
copies some code from usb_kill_urb, to make such unlinks wait until the
host control
With 2.6.10 getting warning about ohci_restart() defined and not used
if !CONFIG_PM. Safe to just get rid of the declaration.
Signed-off-by: Stephen Hemminger <[EMAIL PROTECTED]>
diff -Nru a/drivers/usb/host/ohci-hcd.c b/drivers/usb/host/ohci-hcd.c
--- a/drivers/usb/host/ohci-hcd.c 2004-10
On Tue, 26 Oct 2004, Alex Sanks wrote:
> Hi Alan,
>
> Sorry for the delay on this. Anyway, I'm trying to figure out how to
> duplicate this easily.
>
> Here's what I did (host is vanilla 2.6.9, built with CONFIG_USB_DEBUG and
> CONFIG_USB_SUSPEND:
> - modprobe net2280
> - modprobe g_zero
> - ec
Maybe try inserting skeleton.ko?
Ethan.
On Wednesday 27 October 2004 4:25 am, sunil saggar wrote:
> I was trying to modify the usb-skeleton.c according to
> my device but before that i compiled it in kernel
> space to usb-skeleton.o but when i tried to insert the
> module using insmod iam getting
On Wed, Oct 27, 2004 at 05:03:50PM +0200, Patrick Boettcher wrote:
> I try to get the mentioned USB device to run in Linux. It is a small (USB
> stick sized) device, which only passes through the radio signal to the
> line in. Control is done via USB.
>
> I did some reverse engineering in Windows
Hi,
I try to get the mentioned USB device to run in Linux. It is a small (USB
stick sized) device, which only passes through the radio signal to the
line in. Control is done via USB.
I did some reverse engineering in Windows and I think I determined all
important functions (i.e. bytes :) ).
As i
Greg:
This patch, suggested by Karsten Wiese, converts a few remainder ('%')
operations in the UHCI driver to bitwise-and ('&'). It's not a huge
change, but this is a common idiom in C and it will save a few bytes with
some compilers. Also one of the changes is in an inner loop, so it might
he
On Wed, 2004-10-27 at 01:02, Douglas Gilbert wrote:
> I have been seeing an oops (or badness) since about the lk 2.5
> series if I left my USB Sandisk CF (ImageMate) plug in with a
> mounted file system open when I halted the machine. As the logs
> had already been closed down there was nothing cap
I forgot to stop the OHCI controllers being disabled with a 'setpci
command=0' command on bootup. Now everything works perfectly!
> Please verify if APIC mode can help this case?
>
> Thanks
> Luming
>
> >-Original Message-
> >From: [EMAIL PROTECTED]
> >[mailto:[EMAIL PROTECTED] On Beha
I was trying to modify the usb-skeleton.c according to
my device but before that i compiled it in kernel
space to usb-skeleton.o but when i tried to insert the
module using insmod iam getting an error message
:invalid kernel module...can u plz tell me the
probable cause
thanks
sunil
On Tue, Oct 19, 2004 at 03:33:52PM -0700, David Brownell wrote:
> On Tuesday 19 October 2004 2:14 pm, Ben Dooks wrote:
> > > If you're up for it, I'd rather see a generic hook for
> > > turning port N power on/off ... just hang a method in
> > > the "struct ohci_hcd", and when it's there ohci-hub.c
On 26 Oct 2004 at 09h10, David Brownell wrote:
Hi,
> What's wrong there is emitting voluminous diagnostics for
> something that's not an error ... the root hub is suspended,
> and as with any suspended device, you can't talk to it.
Btw, there's something else wrong, because the root hub shouldn
Mike Christie wrote:
James Bottomley wrote:
On Tue, 2004-10-26 at 14:08, Mike Christie wrote:
The null state and and oops are becuase of this
http://marc.theaimsgroup.com/?l=linux-scsi&m=109733573729283&w=2
Oh yeah. that patch is not correct, but if you correctly modify it to
use device_for_each_c
Hello All,
I have downloaded isp bingo version and i am able to compile and load on my ppc 750
based board with linux 2.4.24 .
The driver is able to detect all usb devices successfully.
I am also having one Creative webcam, i am able to load the appropriate driver for the
webcam, i am running
On 26 Oct 2004 at 09h10, David Brownell wrote:
Hi,
> What's wrong there is emitting voluminous diagnostics for
> something that's not an error ... the root hub is suspended,
> and as with any suspended device, you can't talk to it.
> The descriptor read logic can skip retries in that case, and
>
36 matches
Mail list logo
