Hi,
I am working on Hynix ARM based SOC with USB type B. We are using Linux as
OS for the same. I need to Implement Mass storage device protocole for our
system. Hynix Provides
Hardware Based enumeration. To use USB device as mass storage Device, How to
change the
Device Class and bInterfa
Hi all,
A quick question. I am trying to get the gadgetfs up on my dev board. I
loaded the Low level controller driver, and loaded the gadgetfs module
over it. Cant see to see the /dev/gadgetfs/ directory. Am i missing
something. New to gadgetfs...any docs on the gadgetfs usage?
warm regards,
Hi all,
A quick question. I am trying to get the gadgetfs up on my dev board.
I loaded the Low level controller driver, and loaded the gadgetfs module
over it. Cant see to see the /dev/gadgetfs/ directory. Am i missing
something. New to gadgetfs...any docs on the gadgetfs usage?
warm regards,
On Thu, 2006-02-16 at 17:12 +, Russell King wrote:
> This is probably an idiotic question, but if there's something in the
> scsi release handler can't be called in non-process context, why can't
> scsi queue up the release processing via the work API itself, rather
> than having to have this a
On Thu, Feb 16 2006, James Bottomley wrote:
> On Thu, 2006-02-16 at 18:18 +, Russell King wrote:
> > Maybe implementing it as a helper function would be the best and
> > simplest solution?
> >
> > static void scsi_release(struct device *dev)
> > {
> > schedule_release_process(dev, scsi_rel
On Thu, 2006-02-16 at 18:09 +, Russell King wrote:
> where scsi_release() is the function called by the device model on the
> last put of a scsi device.
>
> I guess is more or less what you're trying to do invasively via the
> driver model.
Yes ... except I think more than just SCSI has the p
Russell King wrote:
On Wed, Feb 15, 2006 at 08:56:00PM -0500, James Bottomley wrote:
[...]
OK, this is what I'm proposing as the device model fix. What it does is
thread context checking APIs throughout the device subsystem. SCSI can
then use it simply via device_put_process_context().
[...]
On Wed, Feb 15, 2006 at 08:56:00PM -0500, James Bottomley wrote:
> On Tue, 2006-02-14 at 10:34 -0600, James Bottomley wrote:
> > Well, I can't solve the problem that it requires memory allocation from
> > IRQ context to operate. Based on that, it's an unsafe interface. I'm
> > going to put it ins
On Thu, Feb 16, 2006 at 10:14:31AM -0800, James Bottomley wrote:
> On Thu, 2006-02-16 at 18:09 +, Russell King wrote:
> > where scsi_release() is the function called by the device model on the
> > last put of a scsi device.
> >
> > I guess is more or less what you're trying to do invasively vi
On Thu, Feb 16, 2006 at 09:57:32AM -0800, James Bottomley wrote:
> On Thu, 2006-02-16 at 17:12 +, Russell King wrote:
> > This is probably an idiotic question, but if there's something in the
> > scsi release handler can't be called in non-process context, why can't
> > scsi queue up the releas
On Thu, 2006-02-16 at 18:18 +, Russell King wrote:
> Maybe implementing it as a helper function would be the best and
> simplest solution?
>
> static void scsi_release(struct device *dev)
> {
> schedule_release_process(dev, scsi_release_process);
> }
>
> where schedule_release_process()
On Tue, 2006-02-14 at 10:34 -0600, James Bottomley wrote:
> Well, I can't solve the problem that it requires memory allocation from
> IRQ context to operate. Based on that, it's an unsafe interface. I'm
> going to put it inside SCSI for 2.6.16, since it's better than what we
> have now, but I don
Andrew,
Your instructions do not work on Slack 10.1 (2.6.15.1 kernel). Joydev is
loaded automatically and device node is created, however no keystrokes are
registered.
Out of curiosity, I loaded an older Gentoo livecd I had lying around. And
the joypad worked exactly like you described.
O
Dear Alan,
>> After that see the Table 5-1. Low-speed Control Transfer Limits.
>> Even though there are a total of 43 bytes to be transferred, I
observe
>> that data payload is less that 8 bytes some times which is against
the
>> above rule in 5.5.3.
>
>Where do you get that 43 from?
I got it th
On 15.02.2006 04:19, Greg KH wrote:
> On Sat, Feb 11, 2006 at 03:52:27PM +0100, Hansjoerg Lipp wrote:
>
>>From: Tilman Schmidt <[EMAIL PROTECTED]>, Hansjoerg Lipp <[EMAIL PROTECTED]>
>>
>>This patch prepares the kernel build infrastructure for addition of the
>>Gigaset ISDN drivers. It creates a M
Hi Olav,
just a short question in between:
where did you find anythin about completion code 0xf ???
According to the ISP116x manual this doesn't exist (but is definitly used)
?
Thank you and best regards,
Peter
On Tue, 14 Feb 2006, Olav Kongas wrote:
>
>
> On Mon, 13 Feb 2006, Peter Wip
尊敬的负责人(经理/财务)您好!
我是深圳建兴实业发展有限公司;在我公司有着良好的
社会关系。业务:贵公司平时在作帐及销售方面是需要用到一些票
据如(普通商品发票、地税、建筑安装、其它服务、广告、运输
发票)等……。如金额开大可算优惠多多,并建议长欺的合作。
在我公司成立多年一直坚持以信用;所开绝对是真票。在合作以
代办的方式提供到位的服务,如贵公司有些愚感或担心,可在网上
查询或拿去税务确认后再付款,其它相关事项还可进一步协商 。
以真成的希望贵公司共同发展,必成永久的朋友。
欢迎来电咨询、洽谈!联 系 人 :叶先生 手 机 :13006707981
Greetings!
The email sent to <[EMAIL PROTECTED]>, will not be delivered. Squire,
Sanders prohibits sending or
receiving of executable attachments via email due to the prevalence of
viruses that propagate
via this method. Do not zip your files and try again as that will not
circumvent this prohi
(Originally posted to linux-usb-users, reposted on suggestion by a
linux-usb-devel list member.)
I'm working to bring up Linux on a locally-designed embedded system that uses
the MPC8245 (a ppc 603e) and an NEC 720101. The CPU and same code base work
fine with an ALi chip.
I'm using 2.4.22,
On Thu, 16 Feb 2006, Jean-Philippe Mengual wrote:
> Hi,
> Well it's very strange, but it seems the problem is physical. I was
> said tha]s very rare, and the person who made my computer doesn't
> understand. I'll do a new check with Windows, to see if USB is known.
That's a good idea.
> If it is
On Thu, 16 Feb 2006, Mukund JB. wrote:
> Yes, I have a specific question regarding the control transfers in USB
> 2.0 specifications.
> Please refer to following paragraph in 5.5.3 Control Transfer Packet
> Size Constraints:-
>
> An endpoint must always transmit data payloads with a data field le
Hi,
Well it's very strange, but it seems the problem is physical. I was
said tha]s very rare, and the person who made my computer doesn't
understand. I'll do a new check with Windows, to see if USB is known.
If it is, problem isn't physical. Anyway if it is it's happent for a
short time, since 2 ye
Hi,
I found one more minor bug in EHCI driver.
In the file ehci.h struct ehci_iso_stream has the field u8 interval;
But accordingly with standard bInterval for ISO endpoints can be value
from 1 to 16
It means that interval in micro-frames can be from 2^(1-1) = 1 to
2^(16-1).
It obviously more th
Hello Olav,
thank you for your support. I've applied your patch (with some minor
changes to make it compile). I've also placed the "early out" code into
the packet trace functions.
The bad think was that I can't even detect the device in question when
packet tracing is enabled..
I than made s
Also Andrea,
If the Function device is MASS storage compliant, you will not require
any additional driver.
Just plugin and you will be able to mount the Flash drive on the Linux
Box.
Mukund Jampala
>-Original Message-
>From: [EMAIL PROTECTED]
[mailto:linux-usb-devel-
>[EMAIL PROTECTED]
Andrea,
Where is the example code?
I guess you missed the attachment.
Header and structure are not clear. Please add clarity.
Or else paste in the pastebin site below and forward me the link.
http://pastebin.com
Regards,
Mukund Jampala
>-Original Message-
>From: [EMAIL PROTECTED]
[mailt
Hello,
I'm writing driver for jogger mp3 player, I read the linux usb documents
and I saw the example code but I don't understand what is the header and
structure I need. I wrote this example code as try but compilation
report very much error.
Thanks
Andrea Beciani
/*
* Jogger mp3 player driver v
Dear Randy,
>> Can some BIG HEAD help on this?
>> I guess it is the 2.2.6 kernel might have had the USB initial USB
Stack.
>> i.e. Linus initial USB Mouse debugging STACK.
>> Can some one please help me with a x86 dist. which had this initial
>> version of USB stack.
>
>What are your specific que
On Wed, Feb 15, 2006 at 09:13:57AM -0800, Greg KH wrote:
> On Wed, Feb 15, 2006 at 01:08:41PM +0100, Henk Vergonet wrote:
> >
> > Hi,
> >
> > When I am compiling an out of tree USB driver I get a linker error:
> >
> > *** Warning: "usb_register_driver"
> > [.../nongnu.org/yealink-module/yealink.
29 matches
Mail list logo