David Brownell wrote:
> I just found out about these Linux drivers ... likely of interest
> if you're working with USB OTG designs from Mentor Graphics:
>
> http://www.mentor.com/products/ip/usb/usb20otg/usb-otg-driver.cfm
>
> The drivers are GPL'd, and presumably can be made to work with the
> F
Jeff Pitman wrote:
> Hi:
>
> I'd like to write a driver for the following USB Serial device:
>
> T: Bus=02 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
> D: Ver= 1.10 Cls=ff(vend.) Sub=ff Prot=ff MxPS= 8 #Cfgs= 1
> P: Vendor=067b ProdID=2313 Rev= 0.04
> S: Manufacturer=Prolific Techn
Andre Renaud writes:
> On Fri, 2005-04-22 at 09:21 +0200, Lothar Wassmann wrote:
> > What type of memory access do you use? I'm using VLIO with the MSC
> > setting 0x7f8c at 99.53MHz memclk. This is probably the only setup
> > that can guarantee the chips timing requirements.
> >
> > Be aware that
Hello Greg ,
My code does tries to follow coding conventions. I have referred the
CodingStyle doc.The file I sent was a txt file enough to view some
important portions of the code.
I am not sure what you meant by not following coding conventions. It
would be good if you could point the crucial po
Greg/Pete,
This is an updated version of a patch I posted last July (but got
forgotten). It adds various VIDs/PIDs to the ftdi_sio driver,
backported from the 2.6 kernel, and a couple of extras.
* Gude Analog- und Digitalsystems GmbH PIDs.
* Linx Technologies PIDs.
* Inside Accesso contactless
On Thu, 28 Apr 2005, Adam Oldham wrote:
> So in essense, there is no way to change the poll
> interval for devices outside of getting the vendor to
> change the software on the device itself?
> Resubmitting the URB like someone else suggested
> doesn't have any affect, that I can tell.
You need
[Apologies for the repost. I got the linux-usb-devel address wrong.]
Hello,
The attached patch adds some entries to the device tables for the
ftdi_sio driver. A better description and signed-off-by line is
included within the attachment.
Please apply. TIA.
--
-=( Ian Abbott @ MEV Ltd.E-mail:
Hello,
The attached patch replaces a couple of redundant macros in the ftdi_sio
driver. Signed off in the attachment.
Please apply. TIA.
--
-=( Ian Abbott @ MEV Ltd.E-mail: <[EMAIL PROTECTED]>)=-
-=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=-
[ftdi_sio] Replaced
On Fri, Apr 29, 2005 at 02:11:51PM +0100, Ian Abbott wrote:
> Greg/Pete,
>
> This is an updated version of a patch I posted last July (but got
> forgotten). It adds various VIDs/PIDs to the ftdi_sio driver,
> backported from the 2.6 kernel, and a couple of extras.
>
> * Gude Analog- und Digita
On Fri, Apr 29, 2005 at 05:48:16PM +0530, [EMAIL PROTECTED] wrote:
>
>
> Hello Greg ,
> My code does tries to follow coding conventions. I have referred the
> CodingStyle doc.The file I sent was a txt file enough to view some
> important portions of the code.
>
> I am not sure what you meant by
On Thursday 28 April 2005 11:59 pm, Phil Dibowitz wrote:
> David Brownell wrote:
> >
> > As always, it's great to see hardware vendors supporting Linux!
>
> I can only hope their drivers are better than their software
That may be so, but it's still much better when vendors support Linux
(with
Hi there,
i cannot connect my SonyEricsson T68 on bluetooth
root:~# rfcomm connect 0 00:09:D9:26:70:46 2
(((on my phone accept and enter the pin:)))
Can't connect RFCOMM socket: Resource temporarily unavailable
root:~# (((I tried it as rfcomm connect 0 00:09:D9:26:70:46 1 as well)))
any ideas?
Szilágyi Szilveszter írta:
Hi there,
i cannot connect my SonyEricsson T68 on bluetooth
root:~# rfcomm connect 0 00:09:D9:26:70:46 2
(((on my phone accept and enter the pin:)))
Can't connect RFCOMM socket: Resource temporarily unavailable
root:~# (((I tried it as rfcomm connect 0 00:09:D9:26:70:
On Tue, Apr 26, 2005 at 11:57:34AM -0400, Alan Stern wrote:
> On Tue, 26 Apr 2005, Roman Kagan wrote:
>
> > On Mon, Apr 25, 2005 at 04:01:07PM -0400, Alan Stern wrote:
> > > I think usb_driver_claim_interface is correct as it stands. It was a
> > > mistake to leave out from usb_driver_release_in
Hi Szilagyi,
> i cannot connect my SonyEricsson T68 on bluetooth
> root:~# rfcomm connect 0 00:09:D9:26:70:46 2
> (((on my phone accept and enter the pin:)))
> Can't connect RFCOMM socket: Resource temporarily unavailable
> root:~# (((I tried it as rfcomm connect 0 00:09:D9:26:70:46 1 as well)
On Thu, Apr 28, 2005 at 02:36:39PM -0400, Alan Stern wrote:
> Here is a fix for driver_detach(). It's a little ugly because it avoids
> using the klist iterator, but there's no way around it -- the iterator
> simply can't be made to work here. Not only does it prevent
> device_release_driver() fr
On Thursday 28 April 2005 10:47 pm, Brian Beardall wrote:
> >But they don't lock up other OHCI implementations? Do the 756 errata
> >have any light to cast on this?
>
> The 756 Errata doesn't expain this behavior. ...
OK, then given that it's intermittent, it's probably something
else going on
On Thursday 28 April 2005 10:20 pm, ma kalven wrote:
>
> My kernel is 2.6.11
> I added this patch:
> [linux-usb-devel] S3C24XX USB controller Ben Dooks
>
> when compile the kernel I found not ohci-s3c2410.o
> created.
Just "modprobe ohci-hcd".
-
On Wed, Apr 27, 2005 at 04:14:08PM -0700, Patrick Mansfield wrote:
> On Wed, Apr 27, 2005 at 05:21:10PM -0400, Alan Stern wrote:
>
> > David's right. Why did kobject_hotplug() move out of kobject_add() and
> > into its callers sometime after 2.6.11? In particular the invocation in
> > device_ad
On Fri, 29 Apr 2005, Roman Kagan wrote:
> On Tue, Apr 26, 2005 at 11:57:34AM -0400, Alan Stern wrote:
> > On Tue, 26 Apr 2005, Roman Kagan wrote:
> >
> > > On Mon, Apr 25, 2005 at 04:01:07PM -0400, Alan Stern wrote:
> > > > I think usb_driver_claim_interface is correct as it stands. It was a
>
On Friday 29 April 2005 11:23 am, Roman Kagan wrote:
>
> ... instead of trying to make sure the attributes are available via
> sysfs at hotplug time, we can use another means to pass them to hotplug:
> we can add a routine, which, when called from the .hotplug function
> and given pointers to stru
Hi all,
i cannot connect my SonyEricsson T68 on bluetooth
root:~# rfcomm connect 0 00:09:D9:26:70:46 2
(((on my phone accept and enter the pin:)))
Can't connect RFCOMM socket: Resource temporarily unavailable
root:~# (((I tried it as rfcomm connect 0 00:09:D9:26:70:46 1 as well)))
any ideas?
mo
Am Freitag, 29. April 2005 21:28 schrieb David Brownell:
> On Friday 29 April 2005 11:23 am, Roman Kagan wrote:
> >
> > ... instead of trying to make sure the attributes are available via
> > sysfs at hotplug time, we can use another means to pass them to hotplug:
> > we can add a routine, which,
On Fri, 29 Apr 2005 14:11:51 +0100, Ian Abbott <[EMAIL PROTECTED]> wrote:
> This is an updated version of a patch I posted last July (but got
> forgotten). It adds various VIDs/PIDs to the ftdi_sio driver,
> backported from the 2.6 kernel, and a couple of extras.
Looks fine, added. However, I'
On Fri, Apr 29, 2005 at 09:35:52PM +0200, Oliver Neukum wrote:
> Am Freitag, 29. April 2005 21:28 schrieb David Brownell:
> > On Friday 29 April 2005 11:23 am, Roman Kagan wrote:
> > >
> > > ... instead of trying to make sure the attributes are available via
> > > sysfs at hotplug time, we can use
On Fri, Apr 29, 2005 at 10:23:36PM +0400, Roman Kagan wrote:
> On Wed, Apr 27, 2005 at 04:14:08PM -0700, Patrick Mansfield wrote:
> > On Wed, Apr 27, 2005 at 05:21:10PM -0400, Alan Stern wrote:
> >
> > > David's right. Why did kobject_hotplug() move out of kobject_add() and
> > > into its callers
Am Freitag, 29. April 2005 22:01 schrieb Greg KH:
> > > I'd rather just guarantee that the sysfs device were fully
> > > constructed (attributes and all) before the driver binding and
> > > hotplug stages of enumeration started. That's been a problem
> > > all along, and that's what those recent c
Greg:
This patch was written by David; I have merely regenerated it against the
current source with appropriate modifications.
Alan Stern
Partial OTG support for dummy_hcd, mostly as a framework for further work.
It emulates the new OTG flags in the host and peripheral frameworks, if
that opt
Greg:
This patch makes some cosmetic changes to dummy_hcd:
Minor alterations of comments and whitespace.
Replace USB_PORT_FEAT_xxx with USB_PORT_STAT_xxx. This is
appropriate as the values are stored in a status variable
and they aren't feature indices. Also it
On Friday 29 April 2005 12:35 pm, Oliver Neukum wrote:
> Am Freitag, 29. April 2005 21:28 schrieb David Brownell:
> > On Friday 29 April 2005 11:23 am, Roman Kagan wrote:
> > >
> > > ... add environment variable ...
> >
> > Color me amused. That was the original way to pass information
> > to ho
On Fri, 2005-04-29 at 22:16 +0200, Oliver Neukum wrote:
> Am Freitag, 29. April 2005 22:01 schrieb Greg KH:
> > > > I'd rather just guarantee that the sysfs device were fully
> > > > constructed (attributes and all) before the driver binding and
> > > > hotplug stages of enumeration started. That'
David Brownell wrote:
>On Thursday 28 April 2005 10:47 pm, Brian Beardall wrote:
>
>
>
>>>But they don't lock up other OHCI implementations? Do the 756 errata
>>>have any light to cast on this?
>>>
>>>
>>The 756 Errata doesn't expain this behavior. ...
>>
>>
>
>OK, then given that it
Dave:
Okay, I tried a squeaky-clean copy of 2.6.11-rc3 on my computer with the
SiS motherboard and OHCI controllers. The only thing non-kosher about it
was this change:
--- ohci-hcd.c.orig Fri Apr 29 11:45:12 2005
+++ ohci-hcd.c Fri Apr 29 12:08:10 2005
@@ -726,6 +726,8 @@
}
Vivian Brégier wrote:
> Hello,
>
> I just bought a new mp3 usb player. But when i tested it, I couldn't make
> it work under Linux, i got scsi error: <4 0 0> return code = 0x1007.
>
> After a few google searches, i found about this unusual_devs.h files.
> I inserted code for my device, recomp
Hello Greg ,
Thanks for the help on the missed coding conventions . I will definitely
incorporate those .
I may not be able to send the entire driver code but I can send some
important functions you need to
help me debug the issues. Let me know if this is fine .
Meanwhile , would it be possible
35 matches
Mail list logo
