Hi,
This patch adds some new vendor/product ids for the USB scanner
driver.
It's the same that already went into 2.5.
Bye,
Henning
diff -u -r linux-2.4.21/drivers/usb/scanner.c
linux-2.4.21-newids7/drivers/usb/scanner.c
--- linux-2.4.21/drivers/usb/scanner.c 2003-06-13 16:51:36.0
Hi, folks
I have a question. I have an idea about a device. This device can be considered as a
black box which includes a Linux OS and one or more harddisks that can be
controled(read and write) by the embedded Linux OS. I want the Linux device to
communicate with a Windows OS PC host(read and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 15 Jun 2003 22:24 pm, [EMAIL PROTECTED] wrote:
I think that I can get the hardware device controller Driver from the
manufacturer of the controller and the Windows Host side should has all
support softwares such as USB Driver, Host
Am Sonntag, 15. Juni 2003 14:24 schrieb [EMAIL PROTECTED]:
Hi, folks
I have a question. I have an idea about a device. This device can be
considered as a black box which includes a Linux OS and one or more
harddisks that can be controled(read and write) by the embedded Linux OS. I
want the
Tomita, Haruo wrote:
Thank you very much. I tried your patch.
In VT6202, it was unstable.
OK, so I've had three reports of problems with VT6202.
Looks like I'll need to swap a card... that chip has
given more trouble than all the others combined!
I've tested reasonably extensively with VT6212,
David T Hollis wrote:
Greg KH wrote:
On Thu, Jun 12, 2003 at 09:12:00AM -0400, David T Hollis wrote:
Few minor code tweaks, formatting, etc. Greg, is this in proper
shape for inclusion?
Close, but I think this will break on 2.4.22-pre1, right:
+#if LINUX_VERSION_CODE
The message appears when I mount and unmount the drive:
Device not ready. Make sure there is a disc in the drive.
Do you think its a problem by the firmware?
I want use the device because its a cheap one and the vendor told to fix the
uncorrect file problem.
Thank you, Joschua
On Wed, 11 Jun
On Sun, 15 Jun 2003 [EMAIL PROTECTED] wrote:
The message appears when I mount and unmount the drive:
Device not ready. Make sure there is a disc in the drive.
Do you think its a problem by the firmware?
I want use the device because its a cheap one and the vendor told to fix the
uncorrect
Some minor cleanups. First, some locking in the bus-reset. Next, we move
current_sg into struct us_data (why make more memory allocation issues for
ourselves?). Next, we change sm_state into a normal variable, since it
shouldn't require atomic_t anytmore. Finally, we remove some references to
This patch implements US_PR_DEVICE and US_SC_DEVICE, which have the meaning
'use the device's value -- no override'. This should make maintance
easier, and also allow for those few devices that change their descriptors
depending on what they are connected to.
This will also print a message to
This patch moves the initialization of the struct scsi_device fields
use_10_for_ms and use_10_for_rw into a central place. This allows the
host's slave_configure() function to change them (with effect). This also
collapses two identical sections of code into a single one.
This patch is needed
This patch (a) removes dead code, (b) renames some static functions with
names that are more apropriate for static functions, and (c) implements a
slave_configure() function.
With the patch I just sent to Linus (et al.) to fix the SCSI core to allow
slave_configure() to tweak (meaningfully) the
(Resend due to error in address for linux-scsi.)
This patch moves the initialization of the struct scsi_device fields
use_10_for_ms and use_10_for_rw into a central place. This allows the
host's slave_configure() function to change them (with effect). This also
collapses two identical sections
Dave wrote,
Haruo Thank you very much. I tried your patch.
Haruo In VT6202, it was unstable.
Dave OK, so I've had three reports of problems with VT6202.
Dave Looks like I'll need to swap a card... that chip has
Dave given more trouble than all the others combined!
14 matches
Mail list logo
