Robert Baruch wrote:
>
> All,
>
> The latest release of the SDDR09 driver (in the CVS tree) contains fixes
> for reading 32MB and larger SmartMedia cards. I was able to successfully
> read a fully-loaded 32MB card. Also I added support for 128MB cards.
Hm, I hit the "too big size" BUG() in kmal
All,
The latest release of the SDDR09 driver (in the CVS tree) contains fixes
for reading 32MB and larger SmartMedia cards. I was able to successfully
read a fully-loaded 32MB card. Also I added support for 128MB cards.
--Rob
___
[EMAIL PROTECTED]
Hi William,
If you want to use SmartMedia cards which are 32MB or larger, you
probably want to use this latest driver!
--Rob
/* Driver for SanDisk SDDR-09 SmartMedia reader
*
* $Id: sddr09.c,v 1.16 2001/03/27 22:37:55 groovyjava Exp $
*
* SDDR09 driver v0.1:
*
* First release
*
* Curr
Brad Hards wrote:
>
> "Stephen J. Gowdy" wrote:
> >
> > Hi Brad,
> > Should I add it to our web site then? Where did you sent it?
>
> G'day Stephen,
>
> It went to a stack of places - linux related and USB related.
>
> Linux PR, LWN, Newsforge are covering it so far:
> http://lwn.net/d
> But when I disconnect the cable or turn the camera off after unmounting
> /dev/sda1 which is the contents of my SmartMedia card I get the following
> message on the console on standard error:
>
> uhci: host controller halted. very bad
Not a good sign ... :)
Have you tried the latest patches a
Well, if it's correct, then it's correct, and therefore doesn't need
changing. I'll crawl back into my hole now
Matt
On Thu, Apr 05, 2001 at 11:36:16AM -0700, Greg KH wrote:
> On Thu, Apr 05, 2001 at 11:12:47AM -0700, Matthew Dharm wrote:
> > The comment indicates that the value is identica
LUNs are _supposed_ to be the same, because we register
new host for every storage device.
However, there is a high profile bug here where LUN,ID,Channel
and Host are the same, and I got a monstrous headache
auditing drivers/usb/scsiglue.c, .../usb.c, drivers/scsi/host.c,
etc., all in vain. I fle
On Thu, Apr 05, 2001 at 11:12:47AM -0700, Matthew Dharm wrote:
> The comment indicates that the value is identical to another value used by
> another vendor... if you're changing the value, doesn't the truth of that
> statement change?
Technically yes, but since a device with that id does not exi
Hello,
I have posted the following on the Linux USB users mainling list but got
no response so I am posting it here...
I just downloaded and installed kernel 2.4.3 and tested my Fujifim Finepix
1400 with this new kernel. I find that initially the camera works fine.
But when I disconnect the cab
The comment indicates that the value is identical to another value used by
another vendor... if you're changing the value, doesn't the truth of that
statement change?
Matt
On Thu, Apr 05, 2001 at 11:04:37AM -0700, Greg KH wrote:
> On Thu, Apr 05, 2001 at 10:39:06AM -0700, Matthew Dharm wrote:
>
On Thu, Apr 05, 2001 at 10:39:06AM -0700, Matthew Dharm wrote:
> Not to be pedantic... but doesn't the comment on that line need to be
> changed also?
I don't get it, what should the comment be changed to?
thanks,
greg k-h
--
greg@(kroah|wirex).com
___
Not to be pedantic... but doesn't the comment on that line need to be
changed also?
Matt
On Wed, Apr 04, 2001 at 06:01:24PM -0700, Greg KH wrote:
> Hi,
>
> This patch against 2.4.3 fixes the GoHubs GO-COM232 product id, to match
> the shipping device, not the development device :)
>
> thanks,
Mark McClelland wrote:
> Miles Lane wrote:
>
>
>> Mark McClelland wrote:
>>
>>
>>> Georg Acher wrote:
>>>
> On Sat, Mar 31, 2001 at 10:06:23PM -0500, Pete Zaitcev wrote:
>
>> many users complain (and file bugs) about a flood of
>> the following message:
>>
>> interr
Hi
I am attempting to implement a library that can be linked into
applications wishing to exchange reports with HIDs (specifically UPSs)
over the USB.
So far, it looks like I can identify the particular device on the USB
by parsing /proc/bus/usb/devices, and then open up a channel to the
de
> I have to use Linux kernel version 2.4.1 for my sh architecture.
OK; the patch adding the hcca support was posted pretty
recently, you presumably found it in the archives. Or just
use the latest OHCI driver (from 2.4.3).
> But for my architecture there is a problem with pci_alloc_consistent:
Hello David,
I have to use Linux kernel version 2.4.1 for my sh architecture.
So I have tried to apply your patchs to it. First I have added to
usb-ohci.c file hcca allocation with pci_alloc_consistent (I don't
know if this is a correct procedure but ,in this way, patchs application
doesn'give
Hello David,
I have to use Linux kernel version 2.4.1 for my sh architecture.
So I have tried to apply your patchs to it. First I have added to
usb-ohci.c file hcca allocation with pci_alloc_consistent (I don't
know if this is a correct procedure but ,in this way, patchs application
doesn'give
Miles Lane wrote:
> Mark McClelland wrote:
>
> > Georg Acher wrote:
> >>> On Sat, Mar 31, 2001 at 10:06:23PM -0500, Pete Zaitcev wrote:
> many users complain (and file bugs) about a flood of
> the following message:
>
> interrupt, status 3 frame# NNN
>
> > Here are some thing
I have added another device to the list of working items.
Vendor id 0x573 and Product id 0x4d01
Could someone with this deivce test it. Grab it from
www.emuit.com/webcam.html.
I do have a few people willing to help with a clean up of the driver and fixing
the framerate problems
The proc_ioctl() function in devio.c which invokes the driver specific
ioctl appears to take care of copying the data structure back to user
space (on or about line 1087 of devio.c).
Allen
Mark McClelland wrote:
>
> Allen Barnett wrote:
>
> > + case USBDEVFS_DRIVER_DEVINFO:
> > +
20 matches
Mail list logo
