Brad Hards wrote:
>
> I am writing a driver for the CATC Netmate USB to ethernet chipset.
> I am also going insane.
>
> The basic principle of operation is that a USB interrupt gets delivered when there
>is a
> packet to be received. Then I read it the packet with a bulk transfer. However
>eve
I am writing a driver for the CATC Netmate USB to ethernet chipset.
I am also going insane.
The basic principle of operation is that a USB interrupt gets delivered when there is a
packet to be received. Then I read it the packet with a bulk transfer. However
everytime I
submit the bulk URB, the
> Basically invisible. There's a possible exception for iso scheduling,
> which could arguably be requested at the microframe (1/8 frame,
> frames still taking 1 millisecond). Perhaps webcam and audio
> drivers would want to take advantage of that; or, perhaps not.
>
Don't do this. You can expo
I got assigned a bug report:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=34551
Basically, when user's process loops it does not allow
khubd to run. I found that write() never returns an error,
and did not know if it was safe to change that behaviour.
So, here it is, the best band-aid I c
> > So one question I have: Fork, or Evolve?
>
> I'd prefer Evolve.
>
> It's development for a reason and if it's broken for a bit, it's all the
> more encouragement to fix it.
That's pretty much my preference for the existing HCDs too.
Sounds like that can start pretty much as soon as there'
> After my initial post about 5 days ago about random oopses in both 2.4.2
> and 2.4.3, several replies were sent, one by David Brownell about
> reverting to kernel 2.4.2, with Alan Cox's last pre-patch (ac28), and
> apply pci-pool and ohci patches from 03/23, and enable kernel debugging
> and sla
Addendum -
The last section of my post doesn't quite make sense - I meant to say that
taking that same kernel (2.4.2-ac28 w/ debugging and slab poisoning) and
booting the P5-233 with it (an Asus TXP4 Intel based board with UHCI
controller) doesn't work with the ov511 either.
Brad
__
Hello, all.
As some of you know, I've been pounding at getting the Cyrix MediaGX +
Kernel 2.4.x series + ov511 camera to play nicely together.
A couple notes first, and a little history -
This is a Cyrix MediaGX 233 system, 8GB hard disk (DMA turned off,
wierd/bad things happen with it enabled)
> From: "Tim Jansen" <[EMAIL PROTECTED]>
>
> On Friday 06 April 2001 17:15, you wrote:
> > - Update usbdevfs. Files should be "per-interface", not "per-device",
> > to provide a model that's more consistent with PCI ("per-function").
> > Names should be "stable" and based on topology. (That's
I thought this was just one of my configs ... 2.4.2-ac20
has the same problem. Lack of "devmode" makes it hard
to use usbdevfs from user mode drivers ... nasty.
Seems that the mount options aren't even getting handed
to usbdevfs, though /etc/mtab thinks it passed them to the
kernel ... the kerne
Hi all,
I'm currently writing a driver for some Carry USB
CompactFlash/SmartMedia/MemoryStick Card readers (www.carry.com.tw,
USB-Vendor 0x7CC). I have some doc's under NDA and the CompactFlash part is
already working quite nicely under 2.4.2.
Now I'm doing the SSFDC stuff. Of course I coul
Hi,
With 2.4.3 i could not mount a usbdevfs partitions with devmode or
devgid it always mount with root.root(644). It works fine with 2.2.19
and couldn't not remember when this has been broken with last 2.4.x
--
MandrakeSoft Inc http://www.chmouel.org
-
It is not a linux usb problem. Sometimes caused by trying to place the
compiler executables in a directory where you do not have write
permissions.
___
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
http://lists.sourceforge.net/lists/l
I wanted to compile the libusb, but at ./configure time i receive that error:
#configure: error: installation or configuration problem: C compiler cannot
create executables.
what's the problem and how can I solve it?
Sorry for the double message, but it's a great problem and I can't go on
wit
Greetings,
On 07-Apr-01 David Brownell wrote:
>> I was browsing through the USB Programming Guide at usb.cs.tum.edu, and I
>> was wondering about one thing... I came across usb_control_msg(), and I
>> recall reading on linux-usb-devel@ that it is not safe to call this
>> function
>> from interrup
In general I found those bit functions under-documented
with respect to fundamental call/return information.
What I wanted was a nice set of arbitrary-length bitmap
routines, but there seemed to be several different models
in ... so once I had it working with "zero
indexed bits in BITS_PER_LONG
> I was browsing through the USB Programming Guide at usb.cs.tum.edu, and I
> was wondering about one thing... I came across usb_control_msg(), and I
> recall reading on linux-usb-devel@ that it is not safe to call this function
> from interrupt context (e.g. probe() and handler functions), becaus
> Maybe it´s worthwhile to mention explicitly whether or not this is allowed,
> so new device driver writers won´t fall into the trap of initializing their
> device while in probe().
Doesn't probe() execute in the context of khubd ?
Oliver
__
A co-worker picked up a shiny new Hitachi DZ-MV100A camcorder which
records MPEG2 video and JPEG stills onto 8cm DVD-RAM cartridges. It
has a USB interface which can be used to download images and movies
from the DVD-RAM while it is inserted. I've found that despite the
vendor-specific class
Hi,
I was browsing through the USB Programming Guide at usb.cs.tum.edu, and I
was wondering about one thing... I came across usb_control_msg(), and I
recall reading on linux-usb-devel@ that it is not safe to call this function
from interrupt context (e.g. probe() and handler functions), because i
Hi, David -
is there a special reason why you did not use find_first_zero_bit
for the bitmap?
-- Pete
___
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Gordon McNutt wrote:
>
> Hi,
>
> I've run across the Dynamic Logical Device spec on the USB org site.
> This looks like just the thing for a project I'm working on. However,
> the spec is from 1999, I've never heard any mention of DLD anywhere
> else, I can't find any significant mention of it o
Nnnn-kay... I upgraded to 2.4.3 and didn't have a problem... I'll wait
for more info.
--Rob
> Eric Sandeen wrote:
>
>
>>
>> Hm, I hit the "too big size" BUG() in kmalloc in this version.
>>
>> Loaded module, mounted the device, and tried a cp *.jpg, and it oopsed
>> on that bug. :(
_
23 matches
Mail list logo
