Pantelis Antoniou wrote:
I have a fairly hacked over version of the original USB host driver that
works for 87x/88x.
We have developed our board with MPC880 and we would like
to try to use 8xx USB host interface with kernel version 2.4.25.
I would like to ask you, if we could use your USB hos
Hi,
how can I find out whether support for a particular USB device is in the kernel?
2.6.11 isn't recognizing it automatically and it isn't recognized by
lsusb. I wonder if 2.6.13 might recognize it, but I'd rather find that
out before actually compiling the thing.
I've been trying to find out wh
Hi,
Bill Gatliff writes:
> Odd odd odd. :^)
>
> The only combination which seems to work for me is this:
>
> static struct isp116x_platform_data csb625_isp116x_platform_data = {
> .sel15Kres = 1,
> .int_act_high = 0,
> .int_edge_triggered = 0,
> .no_power_switching = 1,
> };
> ...
> s
Hi,
Michael Kelly writes:
> Bill,
>
> One issue with the PXA255 edge triggering is that you need
> to be sure you poll the state of the interrupt line before you
> re-enable the GPIO interrupt. That way if the device is asking
> for more servicing, you won't miss it since there will be no
> edge
Hello
I am testing a driver under 2.4.30, that originates from Philips, for
their 1761 OTG high-speed chip. I was verifying drivers behaviour in
error-cases, for which I connecetd a high-speed memory stick over a
long cable and a USB analyser. Now, I can pretty easily bring the
controller to a
Lothar:
Lothar Wassmann wrote:
The PXA requires a minimum pulse width of 1 microsecond (Chapter 4-12
of the PXA255 Developers Manual) on a GPIO pin for proper edge
detection. The ISP116x generates a pulse of 167ns in edge triggered
mode. Thus you cannot use the edge triggered mode of the ISP116
On Thursday 30 June 2005 14.12, Bill Gatliff wrote:
> Still doesn't explain why I can't use IRQT_LOW for the IRQ type,
> though...
The pxa does not support level-triggered GPIO interrupts. Thus, the
pxa-specific interrupt code only handles IRQT_RISING and
IRQT_FALLING, it just ignores IRQT_HIGH
On Thu, 2005-06-30 at 14:30 +0200, Robin Farine wrote:
> On Thursday 30 June 2005 14.12, Bill Gatliff wrote:
>
> > Still doesn't explain why I can't use IRQT_LOW for the IRQ type,
> > though...
>
> The pxa does not support level-triggered GPIO interrupts. Thus, the
> pxa-specific interrupt code
At 06:24 AM 6/30/2005, Lothar Wassmann wrote:
Hi,
Michael Kelly writes:
> Bill,
>
> One issue with the PXA255 edge triggering is that you need
> to be sure you poll the state of the interrupt line before you
> re-enable the GPIO interrupt. That way if the device is asking
> for more servicing,
On Wed, 29 Jun 2005, matthieu castet wrote:
> Hi,
>
> I am writing a driver for an usb device, and I want to support multi-device.
> I want to allow some user configurations for the devices, so I use
> module options and module_param_array.
>
> I would like to know if the device are always prob
Hi,
Michael Kelly writes:
> At 06:24 AM 6/30/2005, Lothar Wassmann wrote:
> >Hi,
> >
> >Michael Kelly writes:
> > > Bill,
> > >
> > > One issue with the PXA255 edge triggering is that you need
> > > to be sure you poll the state of the interrupt line before you
> > > re-enable the GPIO interrupt.
On Thu, 30 Jun 2005, Matthias Urlichs wrote:
> Hi, Alan Stern schrub am Wed, 29 Jun 2005 10:46:39 -0400:
>
> > I'm afraid there's no way around it. Timeouts _have_ to work; pretty much
> > every device driver depends on them crucially. The best way to fix this
> > is to take care of those bro
On Thu, 30 Jun 2005, Timor Raiman wrote:
> Hi,
> how can I find out whether support for a particular USB device is in the
> kernel?
>
> 2.6.11 isn't recognizing it automatically and it isn't recognized by
> lsusb. I wonder if 2.6.13 might recognize it, but I'd rather find that
> out before actua
Hi,
Alan Stern:
> Did you really mean that the transfer _did_ time out, but chip issues
> prevent the _unlink_ from working?
>
Exactly. The URBs sit on the ed_rm queue, and they stay there. :-/
> If the unlink is broken then there's pretty much nothing you can do. The
> HCD drivers won't exit
On Thu, 30 Jun 2005 [EMAIL PROTECTED] wrote:
> Hello
>
> I am testing a driver under 2.4.30, that originates from Philips, for
> their 1761 OTG high-speed chip. I was verifying drivers behaviour in
> error-cases, for which I connecetd a high-speed memory stick over a
> long cable and a USB an
On Thu, 30 Jun 2005, Matthias Urlichs wrote:
> > If the unlink is broken then there's pretty much nothing you can do. The
> > HCD drivers won't exit while there are still outstanding URBs. It doesn't
> > matter what's locked or unlocked.
> >
> Umm, not exactly. ;-) If the hub is not locked,
Hi,
Alan Stern:
> usb_disconnect does not disable the chip -- that happens after it returns.
> The only way usb_disconnect interacts with the controller is through the
> hcd_endpoint_disable routine. That in turn does a normal unlink (which
> you say will not work) and then calls the HCD's endp
On Wed, 29 Jun 2005, Jonathan Selby wrote:
> I posted a strange problem a couple of weeks ago and Alan gave me some
> homework to get more data.
>
> I am now back with this data and a few gray hairs in the bargain.
>
> I was having getting an ISO driver to run and we were able to point
> to a
On Thu, 30 Jun 2005, Alan Stern wrote:
> On Thu, 30 Jun 2005, Matthias Urlichs wrote:
>
> > > If the unlink is broken then there's pretty much nothing you can do. The
> > > HCD drivers won't exit while there are still outstanding URBs. It
> > > doesn't
> > > matter what's locked or unlocked.
Hello, Alan
On Thu, 30 Jun 2005, Alan Stern wrote:
> Implying that you are using the 1761 as a host, not as a slave.
Sure:-)
> > Now, I can pretty easily bring the
> > controller to a state when it sets the HALT bit in its queue-head.
>
> That happens when it receives an error or a STALL token
Hi,
Alan Stern:
> There's one other thing I forgot to ask about... Do you know if the URB
> that is refusing to unlink was sent to the root hub, or was it sent to an
> external device? The unlink operation differs between those two cases.
>
It's queued to the device (USB_DT_DEVICE).
--
Matt
Thank you for your response:
the data you requested is enclosed
After shutting down Vmware, Unplugging and re-plugging the device it
failed to read ISO packets.
/proc/bus/usb/devices entry for device from a SuSE
9.3 system:
before running VMware or your driver,
T: Bus=04 Lev=
Hello,
I am trying to use USB Client (Device Driver) support on MX.21 board
(ARM processor) using Freescale patches.
It is Kernel 2.4.20 and I selected "USB Device Support", and I disabled
"Support for USB" (host) else I cannot compile.
Then I wrote VendorID, ProductID, Product Name, Manufactur
On Thu, 30 Jun 2005, jon wrote:
> Thank you for your response:
>
>
> the data you requested is enclosed
The files didn't show any difference as far as I could see.
You didn't answer my last question. If you run and exit from VMware, and
then unplug and replug the device, does the driver work
No response yet; time to escalate...
On Tue, Jun 28, 2005 at 07:46:46PM -0400, Adam Kropelin wrote:
> Here is a somewhat more direct way of solving the same problem. Please
> consider this for merging to mainline ASAP; the feedback loop described
> below makes apcupsd and possibly other hiddev cli
From: Carlo Perassi <[EMAIL PROTECTED]>
Reading this driver I noticed some trailing whitespaces and tabs so I
removed them with some 80th column fitting and a few more similar
things.
Signed-off-by: Carlo Perassi <[EMAIL PROTECTED]>
Signed-off-by: Domen Puncer <[EMAIL PROTECTED]>
---
cypress_m8
Hi
I have a very basic question.
I have written a Kernel driver for an USB device. Now I want to write an
user space application to open the device and get the handle. What will the
parameter(Path) to the "open" function in the user application. How will I
find to
which hub port my device is con
Could someone comment on this please?
From: "KAMBAROV, ZAUR" <[EMAIL PROTECTED]>
Later in this function we check for the nullness of p.qh. So either this
additonal test is needed or the existing one is redundant.
This defect was found automatically by Coverity Prevent, a static analysis tool.
28 matches
Mail list logo
