hi
i am looking for very cheap usb digital io hardware.
(for connecting external electronic cirtuitry like relays or buttons)
i found several devices with windows drivers.
- are there good devices for linux too?
- how can i reverse engineer the protocol?
do i need special usb reverse engineer
Hi,
Can you please tell me, is there any way to map between actual USB port
and device files. Its something like
port 1 ->devicefile1
port 2 ->devicefile2
port 3 ->devicefile3
etc
can you please give us some guidelines on this thru which we can able to
do this.
Thanks.
Shal
On Tue, Feb 08, 2005 at 02:05:04PM +, Steve Hosgood wrote:
>
> Briefly:
> I've written a driver for a USB camera which sends 1600x1200 or 800x600
> images across a USB 2.0 bulk pipe. It works fine in 1600x1200 mode, but
> if switched to 800x600 mode it only gets a couple of frames before it
>
On Wed, Feb 09, 2005 at 04:37:57AM +, [EMAIL PROTECTED] wrote:
> Hello from Gregg C Levine
> One of my less then there staff members came up with an interesting
> project that communicates via the serial protocol (RS232) with its
> host. He selected the Keyspan USA-19 adapter to connect to the
On Wed, Feb 09, 2005 at 07:18:03AM +0100, Olaf Hering wrote:
> On Tue, Feb 08, Greg KH wrote:
>
> > On Tue, Feb 08, 2005 at 05:02:08PM +0100, Olaf Hering wrote:
> > >
> > > The attached USB cam worked once on a powerbook, but never again. I
> > > always get timeouts. Same timeouts happen on uhci
On Tue, Feb 08, Greg KH wrote:
> On Tue, Feb 08, 2005 at 05:02:08PM +0100, Olaf Hering wrote:
> >
> > The attached USB cam worked once on a powerbook, but never again. I
> > always get timeouts. Same timeouts happen on uhci controllers on i386
> > and x86_64. Any idea what could be tweaked to ma
Hello from Gregg C Levine
One of my less then there staff members came up with an interesting project
that communicates via the serial protocol (RS232) with its host. He selected
the Keyspan USA-19 adapter to connect to the host. Now he wants to test the
thing.
We found the pages discussing USB
On Tue, Feb 08, 2005 at 05:02:08PM +0100, Olaf Hering wrote:
>
> The attached USB cam worked once on a powerbook, but never again. I
> always get timeouts. Same timeouts happen on uhci controllers on i386
> and x86_64. Any idea what could be tweaked to make it work?
>
>
> cowberry:~ # cat /proc/
Matthew Dharm wrote:
On Tue, Feb 08, 2005 at 05:40:00PM -0800, Randy.Dunlap wrote:
I wrote code to turn off the 0x80 bit at PCI config space offset 0x47
in DevB, or at least I think I did, but it's not working. Is it being
done too late? The patch is attached.
Matt, did you try this? working for
On Tue, Feb 08, 2005 at 05:46:02PM -0800, Matthew Dharm wrote:
> On Tue, Feb 08, 2005 at 05:40:00PM -0800, Randy.Dunlap wrote:
> > I wrote code to turn off the 0x80 bit at PCI config space offset 0x47
> > in DevB, or at least I think I did, but it's not working. Is it being
> > done too late? The
On Tue, Feb 08, 2005 at 05:40:00PM -0800, Randy.Dunlap wrote:
> I wrote code to turn off the 0x80 bit at PCI config space offset 0x47
> in DevB, or at least I think I did, but it's not working. Is it being
> done too late? The patch is attached.
>
> Matt, did you try this? working for you?
I h
Hi,
Sent to everyone so that build and compile tests will be possible. These
constants are used all over, but only with respect to these usb_*_msg()
functions. Only Greg should need to pull this into a tree, though, to send
upstream.
Thanks,
Nish
Description: Change the units of the timeout cons
Hi,
Sent to everyone so that build and compile tests will be possible. Only Greg
should need to pull this into a tree, though, to send upstream.
Thanks,
Nish
Description: Change the units of the timeout parameter in both usb_control_msg()
and usb_bulk_msg() from jiffies to milliseconds. This is
Hi,
The following patchset (affecting USB, Bluetooth, IrDA, Sound, DVB and W1 --
hence the long To: an Cc: lists...) converts the usb_control_msg() and
usb_bulk_msg() functions to use milliseconds in the timeout parameter instead
of jiffies. This is not a problem for almost all cases, as the reque
Andi Kleen wrote:
On Tue, Feb 08, 2005 at 10:26:51AM -0800, Matthew Dharm wrote:
On Tue, Feb 08, 2005 at 04:34:01PM +0100, Andi Kleen wrote:
So how does one use EHCI on an 8111, if the BIOS disables
it anyway when needed?
E.g., on an IBM IntelliStation A Pro Type 6224?
There's a bit somewhere in th
Hi,
Description: Change units of parameters being passed to usb_control_msg() to
milliseconds. USB_CTRL_{GET,SET}_TIMEOUT's units are changed in a separate patch
such that the the HZ multiplication is no longer necessary.
Signed-off-by: Nishanth Aravamudan <[EMAIL PROTECTED]>
--- 2.6.11-rc3-kj-v
On Tuesday 08 February 2005 11:54 am, Andi Kleen wrote:
> On Tue, Feb 08, 2005 at 11:48:11AM -0800, David Brownell wrote:
> > On Tuesday 08 February 2005 11:05 am, Andi Kleen wrote:
> > > My plan was to just drive a normal host2host cable through
> > > debug port. It'll need some hacks, but should
Greg:
This patch contains the changes to the ohci-au1xxx driver.
Alan Stern
Signed-off-by: Alan Stern <[EMAIL PROTECTED]>
= drivers/usb/host/ohci-au1xxx.c 1.1 vs edited =
--- 1.1/drivers/usb/host/ohci-au1xxx.c 2005-02-03 00:11:19 -05:00
+++ edited/drivers/usb/host/ohci-au1xxx.c
Greg:
This patch contains the changes to the sl811-hcd driver.
Alan Stern
Signed-off-by: Alan Stern <[EMAIL PROTECTED]>
= drivers/usb/host/sl811-hcd.c 1.7 vs edited =
--- 1.7/drivers/usb/host/sl811-hcd.c2005-01-28 17:14:07 -05:00
+++ edited/drivers/usb/host/sl811-hcd.c 2005-02-08
Greg:
This patch contains the changes to the ohci-sa driver.
Alan Stern
Signed-off-by: Alan Stern <[EMAIL PROTECTED]>
= drivers/usb/host/ohci-sa.c 1.45 vs edited =
--- 1.45/drivers/usb/host/ohci-sa.c 2005-01-11 12:14:58 -05:00
+++ edited/drivers/usb/host/ohci-sa.c
Greg:
This patch contains the changes to the ohci-pxa27x driver.
Alan Stern
Signed-off-by: Alan Stern <[EMAIL PROTECTED]>
= drivers/usb/host/ohci-pxa27x.c 1.7 vs edited =
--- 1.7/drivers/usb/host/ohci-pxa27x.c 2005-01-11 12:14:58 -05:00
+++ edited/drivers/usb/host/ohci-pxa27x.c
Greg:
This patch contains the changes to the ohci-ppc-soc driver.
Alan Stern
Signed-off-by: Alan Stern <[EMAIL PROTECTED]>
= drivers/usb/host/ohci-ppc-soc.c 1.1 vs edited =
--- 1.1/drivers/usb/host/ohci-ppc-soc.c 2005-01-25 16:17:10 -05:00
+++ edited/drivers/usb/host/ohci-ppc-soc.c
Greg:
This patch contains the changes to the ohci-omap driver.
Alan Stern
Signed-off-by: Alan Stern <[EMAIL PROTECTED]>
= drivers/usb/host/ohci-omap.c 1.23 vs edited =
--- 1.23/drivers/usb/host/ohci-omap.c 2005-01-20 05:30:19 -05:00
+++ edited/drivers/usb/host/ohci-omap.c 2005-02-08
Greg:
This patch contains the changes for the ohci-lh7a404 driver.
Alan Stern
Signed-off-by: Alan Stern <[EMAIL PROTECTED]>
= drivers/usb/host/ohci-lh7a404.c 1.8 vs edited =
--- 1.8/drivers/usb/host/ohci-lh7a404.c 2005-01-11 12:14:58 -05:00
+++ edited/drivers/usb/host/ohci-lh7a404.c
On Tuesday 08 February 2005 11:11 am, Randy.Dunlap wrote:
> David Brownell wrote:
> > Do you actually have a debug port driver for Linux? And some
> > hardware that it can talk to?
> >
> > I started looking at that issue a while back:
>
> I started looking into one last week.
Great, I'll be gla
Greg:
This patch contains the changes for the core hcd-pci file and the uhci-hcd
driver.
Alan Stern
Signed-off-by: Alan Stern <[EMAIL PROTECTED]>
= drivers/usb/core/hcd-pci.c 1.74 vs edited =
--- 1.74/drivers/usb/core/hcd-pci.c 2005-01-23 04:30:11 -05:00
+++ edited/drivers/usb/co
Greg:
This patch contains the changes for the dummy-hcd driver.
Alan Stern
Signed-off-by: Alan Stern <[EMAIL PROTECTED]>
= drivers/usb/gadget/dummy_hcd.c 1.24 vs edited =
--- 1.24/drivers/usb/gadget/dummy_hcd.c 2005-01-11 12:14:57 -05:00
+++ edited/drivers/usb/gadget/dummy_hcd.c
Greg:
This patch contains the changes to the hcd glue layer in usbcore. It is a
prerequisite for all the other patches (which are all otherwise
independent).
Alan Stern
Signed-off-by: Alan Stern <[EMAIL PROTECTED]>
= drivers/usb/core/hcd.c 1.187 vs edited =
--- 1.187/drivers/usb/co
Greg and others:
This series of patches centralizes much of the functionality required for
creating, registering, and removing hcd and bus structures into the core.
It removes a lot of duplication among various HC drivers. It also removes
a class of bugs in which drivers would call their stop(
On Tue, Feb 08, 2005 at 08:30:51PM +0100, Andi Kleen wrote:
> On Tue, Feb 08, 2005 at 02:25:14PM -0500, Alan Stern wrote:
> > On Tue, 8 Feb 2005, Matthew Dharm wrote:
> >
> > > Of course, that still doesn't change the fact that we've got a bug that
> > > can
> > > be hit by other types of probing
On Tue, 8 Feb 2005, Andi Kleen wrote:
> On Tue, Feb 08, 2005 at 02:25:14PM -0500, Alan Stern wrote:
> > On Tue, 8 Feb 2005, Matthew Dharm wrote:
> >
> > > Of course, that still doesn't change the fact that we've got a bug that
> > > can
> > > be hit by other types of probing errors that will cau
On Tue, Feb 08, 2005 at 11:48:11AM -0800, David Brownell wrote:
> On Tuesday 08 February 2005 11:05 am, Andi Kleen wrote:
> > My plan was to just drive a normal host2host cable through
> > debug port. It'll need some hacks, but should not be too bad.
>
> I'd have expected some of them to _be_ "de
On Tuesday 08 February 2005 11:05 am, Andi Kleen wrote:
> My plan was to just drive a normal host2host cable through
> debug port. It'll need some hacks, but should not be too bad.
I'd have expected some of them to _be_ "debug devices" in fact,
but I'm not sure how common that is. My extremely l
On Tue, Feb 08, 2005 at 02:25:14PM -0500, Alan Stern wrote:
> On Tue, 8 Feb 2005, Matthew Dharm wrote:
>
> > Of course, that still doesn't change the fact that we've got a bug that can
> > be hit by other types of probing errors that will cause an OOPS.
>
> If you're talking about the driver-mode
On Tue, 8 Feb 2005, David Brownell wrote:
> > It leads to a
> > compiler warning when converting the u64 resource[0].start to (void
> > __iomem *) hcd->regs (cast to pointer from integer of different size).
>
> What compiler? I've never seen such a warning.
The omap toolchain version of gcc-3.
On Tue, 8 Feb 2005, Matthew Dharm wrote:
> Of course, that still doesn't change the fact that we've got a bug that can
> be hit by other types of probing errors that will cause an OOPS.
If you're talking about the driver-model-related bug that Andi originally
reported, it has already been fixed.
Andi Kleen wrote:
The only USB debug device that I have been able to find is
this one:
http://store.yahoo.com/plxtech/net20dg.html
I've ordered one and will be beginning on supporting it RSN.
It would be much nicer to try to support the standard host2host cables.
This would there would be actually
> The only USB debug device that I have been able to find is
> this one:
> http://store.yahoo.com/plxtech/net20dg.html
> I've ordered one and will be beginning on supporting it RSN.
It would be much nicer to try to support the standard host2host cables.
This would there would be actually a chance
David Brownell wrote:
On Tuesday 08 February 2005 1:03 am, Andi Kleen wrote:
BTW EHCI works, you just shouldn't use any USB 2.0 devices.
That is, the root hub "switch to the companion controller"
works, but not any other traffic? Then there's no point...
But there are valid reasons in some cases
On Tue, Feb 08, 2005 at 10:11:25AM -0800, David Brownell wrote:
> On Tuesday 08 February 2005 1:03 am, Andi Kleen wrote:
> >
> > BTW EHCI works, you just shouldn't use any USB 2.0 devices.
>
> That is, the root hub "switch to the companion controller"
> works, but not any other traffic? Then the
On Tue, Feb 08, 2005 at 10:20:04AM -0800, Matthew Dharm wrote:
> On Tue, Feb 08, 2005 at 10:03:47AM +0100, Andi Kleen wrote:
> > On Mon, Feb 07, 2005 at 04:02:44PM -0800, Matthew Dharm wrote:
> > > On Tue, Feb 08, 2005 at 12:19:19AM +0100, Andi Kleen wrote:
> > > > Remove useless AMD 8111 EHCI USB
On Tue, Feb 08, 2005 at 10:26:51AM -0800, Matthew Dharm wrote:
> On Tue, Feb 08, 2005 at 04:34:01PM +0100, Andi Kleen wrote:
> > > So how does one use EHCI on an 8111, if the BIOS disables
> > > it anyway when needed?
> > > E.g., on an IBM IntelliStation A Pro Type 6224?
> >
> > There's a bit some
On Tuesday 08 February 2005 1:13 am, [EMAIL PROTECTED] wrote:
> David Brownell <[EMAIL PROTECTED]> said:
>
> > On Wednesday 02 February 2005 5:35 am, [EMAIL PROTECTED] wrote:
> > >
> > > Hi,
> > > It seems that under some conditions when a usb device is physically
> > > disconnected and there ar
On Tue, Feb 08, 2005 at 04:34:01PM +0100, Andi Kleen wrote:
> > So how does one use EHCI on an 8111, if the BIOS disables
> > it anyway when needed?
> > E.g., on an IBM IntelliStation A Pro Type 6224?
>
> There's a bit somewhere in the southbridge (sorry would need
> to look it up in the datasheet
On Tue, Feb 08, 2005 at 10:03:47AM +0100, Andi Kleen wrote:
> On Mon, Feb 07, 2005 at 04:02:44PM -0800, Matthew Dharm wrote:
> > On Tue, Feb 08, 2005 at 12:19:19AM +0100, Andi Kleen wrote:
> > > Remove useless AMD 8111 EHCI USB 2.0 errata check. The BIOS disable it
> > > anyways
> > > when needed,
On Tuesday 08 February 2005 1:03 am, Andi Kleen wrote:
>
> BTW EHCI works, you just shouldn't use any USB 2.0 devices.
That is, the root hub "switch to the companion controller"
works, but not any other traffic? Then there's no point...
> But there are valid reasons in some cases to want to ha
On Tuesday 08 February 2005 8:38 am, Alan Stern wrote:
> On Mon, 7 Feb 2005, David Brownell wrote:
> >
> > Print out the hardware address; match /proc/iomem. There was a patch
> > submitted to make that happen, maybe it got lost somewhere.
>
> Okay. ohci-omap.c doesn't ever call ioremap(); it s
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.
I'd better get busy building a custom kernel!
I can provide a listing of the contents of /proc/bus/usb/devices right
now th
No luck with remote console (no serial - its a laptop and I couldn't get
netconsole to work yet.)
In case it might help someone - I worked around the problem for now by
modifying FC3 rc.sysinit/local to load usb-storage later.
Also, I see another strange thing with usb-storage -It prints the belo
On Mon, 7 Feb 2005, David Brownell wrote:
> > Something else has come up. In that dev_info() message in usb_add_hcd(),
> > where it prints out the iomem or iobase value... For the memory-mapped
> > I/O case, does it make more sense to print the original I/O address or the
> > value of the mapped
The attached USB cam worked once on a powerbook, but never again. I
always get timeouts. Same timeouts happen on uhci controllers on i386
and x86_64. Any idea what could be tweaked to make it work?
cowberry:~ # cat /proc/bus/usb/devices
T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12
> So how does one use EHCI on an 8111, if the BIOS disables
> it anyway when needed?
> E.g., on an IBM IntelliStation A Pro Type 6224?
There's a bit somewhere in the southbridge (sorry would need
to look it up in the datasheet and you can do that as well yourself ;-)
If you set that bit before t
On Tue, 8 Feb 2005, Steve Hosgood wrote:
> I've written a driver for a USB camera which sends 1600x1200 or 800x600
> images across a USB 2.0 bulk pipe. It works fine in 1600x1200 mode, but
> if switched to 800x600 mode it only gets a couple of frames before it
> wedges.
>
> I took a look at the U
Andi Kleen wrote:
On Mon, Feb 07, 2005 at 04:02:44PM -0800, Matthew Dharm wrote:
On Tue, Feb 08, 2005 at 12:19:19AM +0100, Andi Kleen wrote:
Remove useless AMD 8111 EHCI USB 2.0 errata check. The BIOS disable it anyways
when needed, and when not then the hardware works. This cleans up
the EHCI driv
On Tue, 8 Feb 2005, Gerd v. Egidy wrote:
> Hi,
>
> I've got a usb pen drive and got problems getting it to work.
>
> With Windows and 2.4 the drive works flawless but with 2.6.11-rc3 (vanilla)
> I get the attached output (usb debuggin on).
>
> The drive is a newer one from Sharkoon (if that hel
I did post the following discovery to the users list yesterday, but have
since realised that that was probably the wrong place for it. Hope this
*is* the right place to ask, folks. If not, then sorry.
Briefly:
I've written a driver for a USB camera which sends 1600x1200 or 800x600
images across a
David Brownell <[EMAIL PROTECTED]> said:
> On Wednesday 02 February 2005 5:35 am, [EMAIL PROTECTED] wrote:
> >
> > Hi,
> > It seems that under some conditions when a usb device is physically
> > disconnected and there are some pending urbs ehci_endpoint_disable
> > can loop forever in state QH_S
On Mon, Feb 07, 2005 at 04:02:44PM -0800, Matthew Dharm wrote:
> On Tue, Feb 08, 2005 at 12:19:19AM +0100, Andi Kleen wrote:
> > Remove useless AMD 8111 EHCI USB 2.0 errata check. The BIOS disable it
> > anyways
> > when needed, and when not then the hardware works. This cleans up
> > the EHCI dri
58 matches
Mail list logo
