> > What kernel version are you using? And what is the callback for the
> > oops?
> Using 2.4.20-19.8. You're going to tell me to upgrade to 2.6, aren't you? ;)
It's a Red Hat kernel. I am not sure Greg's goodwill covers
that, I suggest you file a bug. Or, reproduce the problem
with a communit
On Wed, Sep 10, 2003 at 02:45:04PM +1000, Mark McDougall wrote:
> Greg KH wrote:
>
> >What kernel version are you using? And what is the callback for the
> >oops?
>
> Sorry, didn't even think to specify. Doh!
>
> Using 2.4.20-19.8. You're going to tell me to upgrade to 2.6, aren't you? ;)
Yup
Greg KH wrote:
>Using 2.4.20-19.8. You're going to tell me to upgrade to 2.6, aren't
you? ;)
Yup :)
OK, I don't have a problem with that, but out of curiosity, were there
known problems with unlink in 2.4.x? or am I more likely doing something
wrong???
Thanks for your response.
Regards,
--
Greg KH wrote:
> What kernel version are you using? And what is the callback for the
> oops?
Sorry, didn't even think to specify. Doh!
Using 2.4.20-19.8. You're going to tell me to upgrade to 2.6, aren't you? ;)
And no oops - just blinking keyboard leds. No message in /var/log/messages.
Regard
On Wed, Sep 10, 2003 at 02:19:56AM +0200, Pavel Machek wrote:
> Hi!
>
> > > > The latter two functions do not exist in -test5. It would helpful if you
> > > > tried to reproduce with a virgin -test5. It would be courteous to state
> > > > what patches you applied on top of the virgin -test5 kern
On Wed, Sep 10, 2003 at 12:38:18PM +1000, Mark McDougall wrote:
> Hi All,
>
> I'm having problems unlinking in my device driver.
>
> My driver submits a number of IN urbs on device open (up to 16) and
> simply appends data in a buffer in the callback function before
> re-submitting another urb
On Wed, Sep 10, 2003 at 03:20:31AM +0100, John Levon wrote:
>
> I'm probably labouring under some fundamental misunderstanding here,
> but I'll plow on regardless.
>
> 83 /* needs to be called with BKL held */
> 84 int usb_probe_interface(struct device *dev)
>
> is exposed to the drive
Hi All,
I'm having problems unlinking in my device driver.
My driver submits a number of IN urbs on device open (up to 16) and
simply appends data in a buffer in the callback function before
re-submitting another urb (not the same one - an 'idle' one).
However, when closing the device and atte
The original message was received at Wed, 10 Sep 2003 11:37:37 +0900 (JST)
from [203.180.63.209]
- The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
(reason: 550 Host unknown)
- Transcript of session follows -
550 5.1.2 <[EMAIL PROTECTED]>... Host
I'm probably labouring under some fundamental misunderstanding here,
but I'll plow on regardless.
83 /* needs to be called with BKL held */
84 int usb_probe_interface(struct device *dev)
is exposed to the driver model. Whilst I've not yet dis-entangled the
call stack that gets here, I
Hi!
> > > The latter two functions do not exist in -test5. It would helpful if you
> > > tried to reproduce with a virgin -test5. It would be courteous to state
> > > what patches you applied on top of the virgin -test5 kernel.
> >
> > Lot of them, but only "revert to -test3 swsusp" should be
This is the Postfix program at host anubis.uji.es.
I'm sorry to have to inform you that the message returned
below could not be delivered to one or more destinations.
For further assistance, please send mail to
If you do so, please include this problem report. You can
delete your own text from
Hi!
> > > The latter two functions do not exist in -test5. It would helpful if you
> > > tried to reproduce with a virgin -test5. It would be courteous to state
> > > what patches you applied on top of the virgin -test5 kernel.
> >
> > Lot of them, but only "revert to -test3 swsusp" should be
> > The latter two functions do not exist in -test5. It would helpful if you
> > tried to reproduce with a virgin -test5. It would be courteous to state
> > what patches you applied on top of the virgin -test5 kernel.
>
> Lot of them, but only "revert to -test3 swsusp" should be important
> he
On Tue, 9 Sep 2003, Georgi Chorbadzhiyski wrote:
> Hello,
> I was able to access my Music Pen mp3 player using usb-storage driver
> in 2.4 without any problems. After updating to 2.6 this was not possible
> anymore. It seems that usb-storage driver in 2.6 detect the device but
> I was unable to ac
Hurry, progress. I finally got the drawer to open. Now knowing status
would be great.
Thank you very much Brad. Your write example was what got me up and
running. Here is the modified version to open the drawer. It's sloppy,
and not complete with regard to checking what drawer, manufacture, etc.
Our virus detector has just been triggered by a message you sent:-
To: [EMAIL PROTECTED]
Subject: Re: Thank you!
Date: Tue Sep 9 18:48:23 2003
One or more of the attachments (application.pif) are on
the list of unacceptable attachments for this site and will not have
been delivered.
Consid
Hi!
> > Upon attempt to swsusp, I get "Unable to handle kernel paging request
> > at virtual address fff4" in usb_device_suspend, called from
> > suspend_device, device_suspend, drivers_suspend, do_software_suspend,
> >
>
> Unfortunately, we don't have a 'taint' flag for when extra patch
On Tue, 2003-09-09 at 03:51, Brad Hards wrote:
> OK, lets try this from the start.
Ok, how bout a completely new start. Not sure if I just was not paying
attention or performing the same tests once modules were loaded.
Either way I can now access the cash drawer via /dev/usb/hiddev0
dmesg shows
Alan Stern wrote:
On Tue, 9 Sep 2003, Georgi Chorbadzhiyski wrote:
I was able to access my Music Pen mp3 player using usb-storage driver
in 2.4 without any problems. After updating to 2.6 this was not possible
anymore. It seems that usb-storage driver in 2.6 detect the device but
I was unable to ac
Hello,
I was able to access my Music Pen mp3 player using usb-storage driver
in 2.4 without any problems. After updating to 2.6 this was not possible
anymore. It seems that usb-storage driver in 2.6 detect the device but
I was unable to access /dev/sda1. "mount -t vfat /dev/sda1 /mnt" returns
this
Hi,
I'm connected with cellular phones (author of MyGnokii/Gammu project). I
have problem now. DKU-5 USB cable for Nokia phones. Serial converter.
Writing/reading/handling dtr and rts. I can't force it to work. I have
some sniffs done in win32, but have problems with understanding them and
writin
Alan Stern wrote:
On Mon, 8 Sep 2003, David Brownell wrote:
When a device stops responding, it's hard to think the
problem is anything other than with the device. (Though
I still don't see where the storage class-specific reset
gets sent by usb-storage, maybe that'd clean up better.)
The reset
Alan Stern wrote:
On Tue, 9 Sep 2003, Baldrick wrote:
Hi Alan, since you didn't squelch those ideas how about this even wilder one:
it seems to me that for IN transfers (I am thinking bulk) it is possible to allocate
no TDs whatsoever!
How about a different radical approach. Remembering tha
On Tue, 9 Sep 2003, David Brownell wrote:
> How about a different radical approach. Remembering that there's
> already a queue of URBs in the HCD glue, it's clear that they don't
> all need to have TDs immediately allocated ... when an endpoint queue
> is "empty enough", the lower level HCD code
On Tue, Sep 09, 2003 at 04:16:42PM +0200, Luca Risolia wrote:
>
> This is the W996[87]CF driver source code in pure text, for submission to
> the Linux kernel 2.4 and 2.6.
>
> The code to be submitted has been sent to the USB manteiner as well.
Please send this as different patches as is documen
On Tue, Sep 09, 2003 at 11:26:30AM +0200, Luca Risolia wrote:
> > On Mon, Sep 08, 2003 at 01:49:02PM +0200, Luca Risolia wrote:
> > > Hello,
> > > I'd like to submit the W996[87]CF driver to the Linux kernel 2.4 and
> > > 2.6. I have already sent an email to Linus, but I don't know whether
> > > he
Arkadiusz Miskiewicz wrote:
4) USB no longer working. Was working fine in vanilla test4.
I'm suspecting this is because of a change to make UHCI
initialization more closely match what EHCI and OHCI do:
kick out pre-OS (BIOS/SMM/...) boot time hooks, then reset.
Try changing uhci_reset() so it call
On Tue, 9 Sep 2003 [EMAIL PROTECTED] wrote:
> Sep 9 11:32:47 cthulhu kernel: hub 1-0:0: debounce: port 1: delay 100ms stable 4
> status 0x101
> Sep 9 11:32:47 cthulhu kernel: hub 1-0:0: new USB device on port 1, assigned
> address 2
> Sep 9 11:32:47 cthulhu kernel: usb-storage: This device (0
On Tue, 9 Sep 2003, Baldrick wrote:
> Hi Alan, since you didn't squelch those ideas how about this even wilder one:
> it seems to me that for IN transfers (I am thinking bulk) it is possible to allocate
> no TDs whatsoever! The TDs are set up in the transfer buffer instead!! For
> example, suppo
On Mon, 8 Sep 2003, Olaf Hering wrote:
> Hi,
>
> any idea how to get this going? First time I got the attached oops.
>
> "Vivitar, Inc."
> traveller DC 4300
> usb.c: USB device 5 (vend/prod 0x784/0x4300) is not claimed by any active driver.
> Initializing USB Mass Storage driver...
> usb.c: reg
This is the W996[87]CF driver source code in pure text, for submission to
the Linux kernel 2.4 and 2.6.
The code to be submitted has been sent to the USB manteiner as well.
There are six files below (separated by "-" lines), in order:
1) w9968cf.h
2) w9968cf.externaldef.h
3) w9968cf_decoder.h
4)
On Tue, 9 Sep 2003, Arkadiusz Miskiewicz wrote:
> On Monday 08 of September 2003 18:38, David Brownell wrote:
> > Try changing uhci_reset() so it calls hc_reset() first,
> > and then does the config space write to get rid of "legacy
> > support mode". That's the sequence it used before, which
>
On Mon, 8 Sep 2003, David Brownell wrote:
> > It seems that a device does not answer in the case of kernel 2.4.
> > However, when operating by kernel 2.6 and two or more devices
> > are connected simultaneously, it operates.
> > I cannot think the error of a device.
>
> I'd almost agree, except
On Sun, 7 Sep 2003, Tomita, Haruo wrote:
> I am also looking at this pattern repeatedly.
> It seems that a device does not answer in the case of kernel 2.4.
> However, when operating by kernel 2.6 and two or more devices
> are connected simultaneously, it operates.
> I cannot think the error of a
On Monday 08 of September 2003 18:38, David Brownell wrote:
> Try changing uhci_reset() so it calls hc_reset() first,
> and then does the config space write to get rid of "legacy
> support mode". That's the sequence it used before, which
> seems odd because it's resetting hardware that it's not y
On Tue, 2 Sep 2003 11:01:49 -0400
Adam Lazur <[EMAIL PROTECTED]> wrote:
> This is a repost of a patch I sent to the linux-usb-devel list ~4 months
> ago.
>
> The patch updates the wIndex field for the printer class GET_DEVICE_ID
> control request to take into account the interface and alternate
>
Tomita, Haruo wrote:
It is because it is hard to generate an error in testing
two simultaneously. When testing simultaneously,
much time is required by the time it generates an error.
This is basically a good thing: the root causes are
getting fixed one by one, so it needs more time before
one of
Oliver Neukum wrote:
Am Samstag, 6. September 2003 15:55 schrieb David T Hollis:
+/* Default ethtool_ops assigned. Devices can override in their bind() routine */
+static struct ethtool_ops usbnet_ethtool_ops = {
+ .get_drvinfo= usbnet_get_drvinfo,
+ .get_link
On Tuesday 09 of September 2003 09:54, Arkadiusz Miskiewicz wrote:
> OK, I'm recompiling it with such change:
[...]
> +reset_hc(uhci);
In meantime I've tested test5 with acpi-irq-fixes.patch from
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test5/2.6.0-test5-mm1/brok
Sep 9 11:32:47 cthulhu kernel: hub 1-0:0: debounce: port 1: delay 100ms stable 4
status 0x101
Sep 9 11:32:47 cthulhu kernel: hub 1-0:0: new USB device on port 1, assigned address 2
Sep 9 11:32:47 cthulhu kernel: usb-storage: This device (054c,002e,0300 S ff P 01)
has an unneeded Protocol entry
Vedran Rodic wrote:
Hi.
This patch went into 2.6 kernel but not in 2.4. It applies to
2.4.23-pre3 cleanly.
This sounds like it should fix my last remaining
"usb_control/bulk_msg: timeout" problems. David?
The patch is fine for 2.4 but it won't get rid of as
many messages. I don't think it'll do
> On Mon, Sep 08, 2003 at 01:49:02PM +0200, Luca Risolia wrote:
> > Hello,
> > I'd like to submit the W996[87]CF driver to the Linux kernel 2.4 and
> > 2.6. I have already sent an email to Linus, but I don't know whether
> > he has the time to answer.
>
> Where do you want this driver to live in th
Your email address was listed as the sender of a message emailed to [EMAIL PROTECTED],
dated 09/09/03 04:29:20, containing the W32/Sobig-F virus in the movie0045.pif
attachment. The action taken was: deleted the attachment.
You may not have sent this virus; some viruses, such as SOBIG, KLEZ, SI
On Monday 08 September 2003 16:30, you wrote:
> On Thu, 4 Sep 2003, Duncan Sands wrote:
> > Hi Alan, yes of course - sorry for the brain fart. Using one QH per
> > endpoint seems like an excellent idea. I had a couple of other silly
> > thoughts about TDs. At the moment they seem too big (they e
V I R U S A L E R T
Our viruschecker found the
W32/[EMAIL PROTECTED]
virus in your email to the following recipient:
-> linux
Delivery of the email was stopped!
Please check your system for viruses,
or ask your system administrator to do so.
For your refe
On Monday 08 of September 2003 18:38, David Brownell wrote:
> > 4) USB no longer working. Was working fine in vanilla test4.
Right now I'm testing on 2.6.0test5.
> Try changing uhci_reset() so it calls hc_reset() first,
OK, I'm recompiling it with such change:
static int uhci_reset(struct usb_h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 09 Sep 2003 09:41 am, William L. Thomson Jr. wrote:
> I tried both with the kernel and modules that RH ships, and with my own
> custom kernel from the RH kernel sources. I do have HIDDEV support and
> it and others were enabled in the kernel I
Greg KH wrote:
> On Mon, Sep 08, 2003 at 11:08:52AM -0500, Borchers, Al (C)(STP) wrote:
> > Try adding a wake_up_interruptible(tty->read_wait) in usbserial.c
> > usb_serial_disconnect().
>
> Hm, that might work, I'll have to try that sometime soon...
You will also need to somehow tell the tty sub
49 matches
Mail list logo
