Hi,
Here's the updated "nousb" patch for vanilla 2.5.41.
It applies with 2 small offsets to 2.5.41-bk3.
Comments/feedback please.
~Randy
--- ./drivers/usb/core/hcd-pci.c.nousb Mon Oct 7 11:24:14 2002
+++ ./drivers/usb/core/hcd-pci.cThu Oct 10 21:23:11 2002
@@ -62,6 +62,9 @@
i
> From: Chris Cheney <[EMAIL PROTECTED]>
> Date: Thu, 10 Oct 2002 22:33:31 -0500
> Debug: sleeping function called from illegal context at include/asm/semaphore.h:119
It needs down() replaced with if (down_trylock()) BUG();
Posslibly fixed already in Greg's tree.
-- Pete
I am running 2.5.41bk3 and I came home tonight and saw this filling
my kern.log, it was also using ~ 100% cpu while doing so.
Debug: sleeping function called from illegal context at include/asm/semaphore.h:119
Call Trace:
[__might_sleep+84/96] __might_sleep+0x54/0x60
[] .rodata+0x10b6/0x1ad4 [u
> To be frank, your disconnection handling is the most outrageous abuse
> of semaphores I've seen in months. But it is correct :-)
Well, I'd like it to be correct in the "it's actually decent code"
department as well. The "in months" part makes me feel a little bit better,
though, as it implies s
Am Freitag, 11. Oktober 2002 01:35 schrieb Greg KH:
> On Fri, Oct 11, 2002 at 01:13:58AM +0200, Oliver Neukum wrote:
> > Hi,
> >
> > this version, though probably horribly broken, should have all features
> > I intended it to have. So could you have a look at this ?
>
> Um, if you know it's broken
On Fri, Oct 11, 2002 at 01:13:58AM +0200, Oliver Neukum wrote:
> Hi,
>
> this version, though probably horribly broken, should have all features
> I intended it to have. So could you have a look at this ?
Um, if you know it's broken, do you still want comments?
> diff -Nru a/drivers/usb/core/hu
Hi,
this version, though probably horribly broken, should have all features
I intended it to have. So could you have a look at this ?
Especially the reevaluation of the device. I am not all that clear about
the generic driver stuff in it.
I am too tired to do coding any further tonight.
On Thu, Oct 10, 2002 at 12:54:48PM +0200, Oliver Neukum wrote:
> Hi,
>
> is there something wrong with hostme.bkbits.net ? My bk pull keeps hanging
> on it.
Don't know, it's working for me.
greg k-h
---
This sf.net email is sponsored by:Thin
On Wed, Oct 09, 2002 at 08:15:27AM -0700, David Brownell wrote:
> > I don't care about any userspace drivers or configuration
> >scripts, they can determine the usbfs location from the driverfs/kfs
> >device already.
>
> Not the last time I looked they couldn't !!
>
> But even if they could,
On Thu, Oct 10, 2002 at 08:53:13AM -0700, David Brownell wrote:
>
> >>>4. May I split usb_disconnect() into an interface and a usb_device part ?
> >>
> >>That needs other work too ... like, shouldn't the driver model core be
> >>handling children-first disconnect, which includes both interface
>
Hi,
here's the new version. It has a lockup bug I am chasing.
Regards
Oliver
You can import this changeset into BK by piping this whole message to:
'| bk receive [path to repository]' or apply the patch as usual.
Oliver Neukum wrote:
>
> in the long and celebrated tradition of sending in patches which happen
> to be completely untested here it is for discussion.
At a first glance it seems the right kind of thing, though it needs a few
more updates. What did you have in mind for testing this?
> This pa
Greg KH wrote:
> On Wed, Oct 09, 2002 at 10:28:49PM -0700, David Brownell wrote:
>
>>>3. Where in the generic device model is the configuration stored
>>> and how can it be manipulated ?
>>
>>There's a readonly driverfs attribute that usb adds to the model.
>>
>>Arguably it should get writable,
>>>4. May I split usb_disconnect() into an interface and a usb_device part ?
>>
>>That needs other work too ... like, shouldn't the driver model core be
>>handling children-first disconnect, which includes both interface
>>shutdown and (for hubs) port shutdown?
>
>
> We do child-first disconnec
Here is the syslog of what happens (produced with scanner.c compiled
with DEBUG on):
Oct 1 01:31:35 basilisk kernel: scanner.c: read stats(0): result:0 this_read:32768
partial:22960 count:45920
Oct 1 01:31:35 basilisk kernel: usb-uhci.c: interrupt, status 3, frame# 1749
Oct 1 01:31:35 basilis
> > > Here's the thought process I originally used:
> > > - Multiple configurations are rare
> > > - Devices won't change substantially between configurations (ie
> > > won't go from a keyboard to a cdrom)
> >
> > That is very likely an invalid assumption.
> > A device might go from webcam to sto
On Thu, Oct 10, 2002, Oliver Neukum <[EMAIL PROTECTED]> wrote:
>
> > I think the big remaining question right now is determining how a
> > configuration should be elected.
> >
> > In my devfs patch a long time ago, I had created an election process
> > where drivers could specify the priority of
Jon Wikne wrote:
>
> Stephan Feder <[EMAIL PROTECTED]> wrote:
>
> > Pieter Nagel wrote:
> > ...
> > > However, I believe for 2.5 the loop should be rewritten as retry loop,
> > > and the function should immediately return whatever it reads, like the
> > > majority of drivers do. As a side effect
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 10 Oct 2002 18:56, JoSH Lehan wrote:
> Hi!
>
> I am looking for a USB passthrough sniffer. I have examined the various
> software USB sniffers available, but they all seem to only be designed
> for sniffing the packet flow between a device an
On Tue, 8 Oct 2002, Greg KH wrote:
>...
> -#define ALOG(lineno,fmt,args...) printk(fmt,lineno,##args)
> -#define LOG(fmt,args...) ALOG((__LINE__),KERN_INFO
>__FILE__":"__FUNCTION__"(%d):"fmt,##args)
> +#define ALOG(fmt,args...) printk(fmt, ##args)
> +#define LOG(fmt,args...) ALOG(KERN_INFO __FIL
Hi,
is there something wrong with hostme.bkbits.net ? My bk pull keeps hanging
on it.
Regards
Oliver
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
Hi folks,
in the long and celebrated tradition of sending in patches which happen
to be completely untested here it is for discussion.
This patch disconnects all interfaces of a device before changing
a configuration and introduces proper locking for that.
Comments?
Regards
> I think the big remaining question right now is determining how a
> configuration should be elected.
>
> In my devfs patch a long time ago, I had created an election process
> where drivers could specify the priority of their support. The highest
> priority won.
>
> Here's the thought process I
Am Donnerstag, 10. Oktober 2002 10:08 schrieb John Tyner:
> Let's try this one. Patch is against 2.5.41.
>
> The device is no longer unregistered in the disconnect but in the
> vicam_free_memory function. This introduced a race with the open call,
> which I believe I've taken care of. I also imple
Hi!
I am looking for a USB passthrough sniffer. I have examined the various
software USB sniffers available, but they all seem to only be designed
for sniffing the packet flow between a device and the PC. I am looking
for a sniffer that can sniff the packet flow between a device and a
separate
Let's try this one. Patch is against 2.5.41.
The device is no longer unregistered in the disconnect but in the
vicam_free_memory function. This introduced a race with the open call, which
I believe I've taken care of. I also implemented the mechanism that I talked
about in my previous email for d
26 matches
Mail list logo
