From: Steve Longerbeam <stevel@mvista.com>
To: baitisj@evolution.com
Cc: Yasushi SHOJI <yashi@atmark-techno.com>,
linux-mips@linux-mips.org, Pete Popov <ppopov@mvista.com>
Subject: Re: USB OHCI device port on Alchemy
Date: Thu, 08 May 2003 14:31:16 -0700 [thread overview]
Message-ID: <3EBACCA4.8030803@mvista.com> (raw)
In-Reply-To: 20030508141457.V30468@luca.pas.lab
[-- Attachment #1: Type: text/plain, Size: 1512 bytes --]
Jeff Baitis wrote:
>Ah, thanks Yashi, I didn't notice this since I was looking in the USB driver
>directories ;)
>
>Steve:
>
>The option seems to be inactive in the kernel config; maybe this patch should
>be applied? Or is there a reason why this option is inaccessible?
>
Jeff, Yashi:
I wrote a similar patch to Yashi's. I've attached it.
Pete: have you applied this to linux-mips yet?
>
>On Thu, May 08, 2003 at 03:53:34PM +0900, Yasushi SHOJI wrote:
>
>
>>At Wed, 7 May 2003 20:31:27 -0700,
>>Jeff Baitis wrote:
>>
>>
>>>Has anyone played with the AU1X00 USB device port yet? If not, what would you
>>>guys suggest that the AU1X00 appear as? USB over Ethernet? Or maybe a simple
>>>dummy device that will perform bulk transfers?
>>>
>>>
>>there are au1000_usbraw.c and au1000_usbtty.c in linux-mips.org's CVS
>>under drivers/char.
>>
>>I'd be excited to see usb storage driver for usb device.
>>
>>as a related topic, does anyone know how usb gadget api is coming? I'm
>>assuming that once usb gadget stabilized and people start using it,
>>we'll be converting au1's usb dev driver to gadget api, no?
>>
This is the first time I've heard of the gadget api, but I'd love to
port the
au1x00 usb dev driver to a full-featured device-side protocol stack, as soon
as the community agrees on one.
When I wrote this driver, I implemented my own, very limited, device and
function api, as there still wasn't an accepted device-side api. But
sounds like
maybe that will finally happen.
Steve
[-- Attachment #2: au1000-usbd.patch --]
[-- Type: text/plain, Size: 1786 bytes --]
Index: arch/mips/config.in
===================================================================
RCS file: /cvsdev/mvl-kernel/linux/arch/mips/config.in,v
retrieving revision 1.20.2.15
diff -u -r1.20.2.15 config.in
--- arch/mips/config.in 19 Feb 2003 11:34:46 -0000 1.20.2.15
+++ arch/mips/config.in 29 Apr 2003 21:56:12 -0000
@@ -391,7 +391,6 @@
define_bool CONFIG_NONCOHERENT_IO y
define_bool CONFIG_PC_KEYB y
define_bool CONFIG_SWAP_IO_SPACE y
- define_bool CONFIG_AU1000_USB_DEVICE y
fi
if [ "$CONFIG_MIPS_PB1500" = "y" ]; then
define_bool CONFIG_MIPS_AU1000 y
Index: drivers/char/Config.in
===================================================================
RCS file: /cvsdev/mvl-kernel/linux/drivers/char/Config.in,v
retrieving revision 1.14.4.11
diff -u -r1.14.4.11 Config.in
--- drivers/char/Config.in 26 Mar 2003 03:51:58 -0000 1.14.4.11
+++ drivers/char/Config.in 29 Apr 2003 21:56:23 -0000
@@ -71,9 +71,13 @@
if [ "$CONFIG_AU1000_UART" = "y" ]; then
bool ' Enable Au1000 serial console' CONFIG_AU1000_SERIAL_CONSOLE
fi
- dep_tristate ' Au1000 USB TTY Device support' CONFIG_AU1000_USB_TTY $CONFIG_AU1000_USB_DEVICE
+ dep_tristate ' Au1000 USB TTY Device support' CONFIG_AU1000_USB_TTY $CONFIG_MIPS_AU1000
if [ "$CONFIG_AU1000_USB_TTY" != "y" ]; then
- dep_tristate ' Au1000 USB Raw Device support' CONFIG_AU1000_USB_RAW $CONFIG_AU1000_USB_DEVICE
+ dep_tristate ' Au1000 USB Raw Device support' CONFIG_AU1000_USB_RAW $CONFIG_MIPS_AU1000
+ fi
+ if [ "$CONFIG_AU1000_USB_TTY" != "n" -o \
+ "$CONFIG_AU1000_USB_RAW" != "n" ]; then
+ define_bool CONFIG_AU1000_USB_DEVICE y
fi
bool 'TXx927 SIO support' CONFIG_TXX927_SERIAL
if [ "$CONFIG_TXX927_SERIAL" = "y" ]; then
next prev parent reply other threads:[~2003-05-08 21:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-08 3:31 USB OHCI device port on Alchemy Jeff Baitis
2003-05-08 6:53 ` Yasushi SHOJI
2003-05-08 21:14 ` Jeff Baitis
2003-05-08 21:31 ` Steve Longerbeam [this message]
2003-05-08 23:41 ` Jeff Baitis
2003-05-08 23:43 ` Pete Popov
2003-05-08 17:40 ` Pete Popov
2003-05-08 21:21 ` Steve Longerbeam
2003-05-09 13:37 ` Brad Parker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3EBACCA4.8030803@mvista.com \
--to=stevel@mvista.com \
--cc=baitisj@evolution.com \
--cc=linux-mips@linux-mips.org \
--cc=ppopov@mvista.com \
--cc=yashi@atmark-techno.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.