On Sat, 12 Feb 2005, Martin Devera wrote:
> Oliver Neukum wrote:
> >Please add a printk for the value of "acm" which is freed in acm_disconnect.
> >
> >
> >
> I did:
> and the result is in usboops.5. It was freed only once ...
Oliver may be on to something. Try using this patch instead of yo
On Thu, Feb 10, 2005 at 12:02:42AM +0100, Brian Murphy wrote:
> David Brownell wrote:
>
> >On Wednesday 09 February 2005 1:57 pm, Brian Murphy wrote:
> >
> >
> >>Listening to your wishes I have the following:
> >>
> >>...
> >>
> >>Presumably you think this should be 2 seperate patches (although t
On Wed, Feb 09, 2005 at 01:13:24PM -0800, Srdjan Sobajic wrote:
> Hi,
>
> I was looking at the scanner.c driver in the 2.4.28 kernel tree, and I
> noticed that it does not use the usb_alloc_urb/usb_free_urb functions
> to allocate the URBs, instead relying on the creation of struct
> scn_usb_data
On Thu, Feb 10, 2005 at 02:24:43PM +0800, Kharisma Esguerra wrote:
> I forgot to say that i'm using Montavista Linux with
> 2.4.20 kernel (and I can't change this, I wish I could).
Then I might suggest you ask Montavista about this issue, as there's not
much we can do here about it :(
thanks,
gr
On Thu, Feb 10, 2005 at 02:20:24PM +0800, Kharisma Esguerra wrote:
> Hi guys, needing your help. (^_^)
>
> I'm currently creating a linux application that would need
> to communicate with a usb-serial device.
>
> I've tested my serial class with a serial printer. My
> class can read and write pro
> Ok, I just retested it with this addition:
> #define DBG_PR_URB(U) dbg("kill_urb @%d addr %p, dev %p
> (%.16s)",__LINE__,U,(U)->dev,(U)->dev?(U)->dev->devpath:"null")
> #define usb_kill_urb(U) do { DBG_PR_URB(U); usb_kill_urb(U); } while(0)
> #define usb_free_urb(U) do { DBG_PR_URB(U); usb_free
Ok, I just retested it with this addition:
#define DBG_PR_URB(U) dbg("kill_urb @%d addr %p, dev %p
(%.16s)",__LINE__,U,(U)->dev,(U)->dev?(U)->dev->devpath:"null")
#define usb_kill_urb(U) do { DBG_PR_URB(U); usb_kill_urb(U); } while(0)
#define usb_free_urb(U) do { DBG_PR_URB(U); usb_free_urb(U); }
On Fri, 2005-01-07 at 09:47 -0800, David Brownell wrote:
> That bug's been there for a while, but not many folk have reported it.
It happens with my SoundBlaster MP3+ on a USB2 hub. Works fine directly
connected, or plugged into a USB1 hub.
> However, a couple weeks back Craig Nadler <[EMAIL PROT
At http://luxik.cdi.cz/~devik/tmp/acm/ I placed communication with
Olived (mbox format)
and extracted attachements (lsusb, debug logs...) for convenience.
File usboops is latest oops without slab debugging (machine also freeze
after
module unload) while usboops.slab is with kernel memory debuggi
On Thu, Sep 23, 2004 at 09:19:11PM +0200, Jan Steinhoff wrote:
> Hi,
>
> I'm working on a kernel 2.6 driver for Synaptics cPad. With kernel >= 2.6.7
> 'rmmod cpad' hangs if called from xterm. This is because Synaptics
> TouchPad driver for XFree86 holds the evdev device of the cPad open, even
> if
On Fri, 11 Feb 2005, Wolfgang Mües wrote:
> If the HC hardware retry logik is "rotten", yes, then the fix belongs to
> the HC driver, I think.
Maybe "rotten" isn't the best word, but there's no question that the
hardware retry logic doesn't cope well with transient errors (spikes)
lasting more t
Hmm, another ARM platform craves aligned buffers. In this case, it turned
up the fact that the alignment handler on a big-endian ARM misbehaves.
Please merge.
- Dave
Go back to aligning RX packets to make the IP layer happy, now that
there's an appropriately platform-specific way to do this. Thi
Hello Alan!
On Thursday 10 February 2005 22:12, Alan Stern wrote:
> On Thu, 10 Feb 2005, Wolfgang Mües wrote:
> > My driver (auerswald) tries so send more than one URB to ep0 at a
> > time! But - I have learned that this does not work reliable,
> > especially with the UHCI hardware. This is mostly
On Fri, 11 Feb 2005, Steve Hosgood wrote:
> > Why do things get wedged instead of failing gracefully?
> >
>
> Well, assuming you hadn't intended to put a smiley on that, they get
> "wedged" because that's how I describe submitting a URB (8 of them
> actually) and none ever calls me back with dat
Duncan Sands wrote:
in particular USE_FW_LOADER is used to avoid compiling
speedtch_find_firmware and speedtch_load_firmware, so the errors you're
seeing means that USE_FW_LOADER is defined. It is defined as follows:
Ah, sorry, I overlooked this. It works when CONFIG_FW_LOADER is set to y or n
bu
On Friday 11 February 2005 9:14 am, Steve Hosgood wrote:
> On Fri, 2005-02-11 at 16:36, Alan Stern wrote:
> > > Meanwhile, I ran my driver with detailed debugging of its own and what I
> > > see is like this:
> > >
> > >
> > > Receive 32768 bytes from camera: add it to the image-buffer
> > >
On Fri, 2005-02-11 at 16:36, Alan Stern wrote:
> > I get wedged as usual and I have to "kill -9" my viewer program from
> > elsewhere in order to rescue the situation.
>
> Why do things get wedged instead of failing gracefully?
>
Well, assuming you hadn't intended to put a smiley on that, they g
Hi Daniel,
> If CONFIG_FW_LOADER is not set, the speedtouch driver causes kernel
> compilation/linking to fail:
>
>LD .tmp_vmlinux1
> drivers/built-in.o(.text+0xcb9b7): In function `speedtch_find_firmware':
> : undefined reference to `request_firmware'
> drivers/built-in.o(.text+0xcba30
Hi,
If CONFIG_FW_LOADER is not set, the speedtouch driver causes kernel
compilation/linking to fail:
LD .tmp_vmlinux1
drivers/built-in.o(.text+0xcb9b7): In function `speedtch_find_firmware':
: undefined reference to `request_firmware'
drivers/built-in.o(.text+0xcba30): In function `speedtc
On Fri, 11 Feb 2005, Steve Hosgood wrote:
> OK, so I compiled a kernel with CONFIG_USB_DEBUG on, installed ehci_hcd
> with debug=2, and ran my camera driver modified to attempt 40 fps reads
> from the camera in 800x600 pixel mode, 8 bits per pixel.
>
> I get wedged as usual and I have to "kill -9
On Fri, 11 Feb 2005, Samuel Colin wrote:
> > I asked because it's possible the contents of that patch were
> > present in one of the ones you used, even though the patch itself
> > was just posted a couple of days ago.
> >
> I tried yesterday a 2.6.10 and a 2.6.11-rc3-bk7 with this patch (and
> e
On Fri, 11 Feb 2005, Martin Devera wrote:
> Hello,
>
> I'm experiencing regular lockups/oopses with my CDMA USB wireless modem.
> On 2.4.29 it is rock stable.
> I already discussed it with Oliver (current ACM driver maintained) and
> he suggested
> me this list (or -dev ?).
Probably he meant li
On Fri, 11 Feb 2005, Nemanja Popov wrote:
> Sorry about unclear question. I'll try to clear out the problem .
> I'm using XScale pxa255 based board with 64 MB RAM running Linux 2.6.7. The
> device I was talking about is consisted of FPGA, CMOS senzor and 256 MB
> SDRAM memory. FPGA's role is to
On Fri, 11 Feb 2005, Marcel Holtmann wrote:
> thanks for the patch, but I am not sure when I will find the time to
> review it completly. However some comments and please don't diff any
> object files.
Thanks for the comments. There's plenty of questions about the
architecture changes so I'll tr
On Thu, 10 Feb 2005, David Brownell wrote:
> On Thursday 10 February 2005 12:08 pm, Alan Stern wrote:
> >
> > "Device not responding" means either that the device
> > isn't working right or that it's disconnected from the bus (or there's a
> > lot of interference on the line, or a hardware f
On Thu, 10 Feb 2005, David Brownell wrote:
> Plus, remember that my original question was whether a "kill the whole
> queue" primitive _would_ be a net simplification. If it weren't for
> the ep0 case, I think the answer would be "yes" ... though it's still
> not clear to me how much of one it'd
On Tue, 2005-02-08 at 15:32, Alan Stern wrote:
> A few details would help, such as the contents of /proc/bus/usb/devices
> and a system log with CONFIG_USB_DEBUG turned on.
>
Sorry for the delay. I had some hard disk problems.
OK, so I compiled a kernel with CONFIG_USB_DEBUG on, installed ehci_
The Thu, 10 Feb 2005 12:17:05 -0500 (EST)
Alan Stern <[EMAIL PROTECTED]> wrote:
> > > It's not clear from what you said; did any of the patches you
> > > used include this one:
> > >
> > > http://marc.theaimsgroup.com/?l=linux-usb-devel&m=110797162426830&w=2
> > >
> > No, I did the tests before
Hi again,
Is there a possibility to force g_file_storage to transfer captured data
directly from device's RAM instead of using file as a backing storage?
This should be used only for downloading data to host (but writing to id
will be good). Data in the device's RAM is stored in raw format (no file
29 matches
Mail list logo
