The blueprint is updated.
You understanding is mostly correct. One patch to makefile is also provided.
For your questions:
1. The targeted host system for Host side utility is Red Hat FC6, Ubuntu MID
distro and Red Flag MID distro.
2. I am not clear about Gutsy repository.
3. The hardware offers the capability. But currently we don't implement it in
SW. The host utility will notify client utility to switch from mass storage
device to Ethernet device through one hacked SCSI command.
Regards,
Henry
________________________________
From: Lynch, Rusty
Sent: 2007年8月4日 0:14
To: Yuan, Hang
Cc: ubuntu-mobile@lists.ubuntu.com
Subject: RE: USB Client Blueprint
Ok, now we are getting somewhere. I still have some clarifying questions, but
in general the below email is much more clear on what you really intend to do.
Please add this level of information to the blueprint.
Just to be sure I understand correctly, you will:
* Provide a new peripheral controller kernel driver
* Provide a patch to the CDC Ethernet gadget kernel driver
* Provide a patch to the file-backed storage gadget kernel driver
* Make a sample suite of both client and host applications available that
use the above kernel components to create a specific solution. This solution
will include a client side application that will allow the user to select which
folder to share, and then use this information to setup a network share drive.
The solution will also include a host side utility that will be presented to
the host system via the mass storage device. If this host application were run
by the host then the host will setup the network over USB connection and mount
the shared drive that the client side utility recently made available.
No my questions:
* What operating systems will the host side utility work on?
* Will all components of the sample suite be pushed into the Gutsy
repository?
* Can the hardware offer both a mass storage device and an Ethernet
device at the same time? If not then how do you plan on working around this
complication to implement the sample solution?
I look forward to your reply, but don’t let this info just stay in this thread.
Update the blueprint.
--rusty
________________________________
From: Yuan, Hang
Sent: Thursday, August 02, 2007 6:36 PM
To: [EMAIL PROTECTED]; Johnson, Charles F
Subject: RE: USB Client Blueprint
1. Peripheral controller driver is a new kernel driver.
2, 3. CDC Ethernet and File-backed storage are patchs to existing kernel gadget
files.
4. Linux utility includes 3 applications. The first one is client utilty. It
runs in MID and provides options for user to select shared folder. The second
one is host utility. It runs in USB host system and mounts the shared folder in
MID. The third one is host installer. It installs the host utility to host
system from MID. The host utility and host installer are saved in MID first.
Mass storage gadget is first used to copy host utility from MID to host system.
Then CDC-EEM/RNDIS gadget is used to set up network connection for file sharing.
We are providing kernel driver and patchs. The utility is a sample to
demonstrate how to use the USB client driver and a reference for further
development as well.
Regards,
Henry
________________________________
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lynch, Rusty
Sent: Wednesday, August 01, 2007 9:49 AM
To: Charles Johnson; ubuntu-mobile@lists.ubuntu.com
Subject: RE: USB Client Blueprint
>From the design diagram I see that there are four new software components.
1. Peripheral Controller Driver: This is the kernel driver I expected
2. CDC Ethernet: Doesn’t this exist in the kernel already?
3. File-backed storage: Doesn’t this exist in the kernel already?
4. Linux utility: What’s this?
I suspect that the two gadget drivers were colored blue (signifying from the
diagram key that they are software components that need to be developed) on
accident, but my real concern is the item labeled “Linux utility”.
The reason for my concern is that I can interpret the blueprint in two ways
(given the extremely sparse text explainations.)
One interpretation basically says:
We are providing the kernel drivers needed so that it is possible to make a
Poulsbo based MID running UME either look like a USB mass storage device, or
like an Ethernet device, but that’s all we are doing. All the rest of the job
is left as an exercise to the person/organization building a specific solution.
In other words if you install a stock UME image on a Poulsbo based mobile
internet device, and then plug it into a PC’s USB port, then nothing will
happen.
Another interpretation basically says:
We are providing the kernel drivers needed so that it is possible to make a
Poulsbo based MID running UME either look like a USB mass storage device, or
like an Ethernet device, and in addition to this we are also providing a
significant amount of user space tools and configurations so that if you
install a stock UME image on a Poulsbo based mobile internet device, and then
plug it into a PC’s USB port, then <<INSERT CORRECT BEHAVIOR HERE>>
BTW, I’m personally ok with the first interpretation, but if the second
interpretation was the real intent then this spec needs a lot more content.
That “Linux utility” component could be a magnitude more work then a simple
peripheral kernel driver (depending what the utility really does.)
--rusty
________________________________
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Charles Johnson
Sent: Wednesday, August 01, 2007 8:23 AM
To: ubuntu-mobile@lists.ubuntu.com
Subject: Re: USB Client Blueprint
I have not seen any additional comments here. The blueprint for USB Client is:
https://blueprints.launchpad.net/ubuntu/+spec/mobile-usb-client
If there are no additional comments, I'm going to ask that this be approved.
--Charlie
On 7/27/07, Johnson, Charles F < [EMAIL PROTECTED]> wrote:
Can folks take a look at the USB Client blueprint again ? The folks
doing the work think they addressed the comments from the previous
round. So if you still need more, please post them to the ubuntu-mobile
lists again. Also this is another late driver. It isn't schededuled to
be Alpha until 1st week of September. Way to late. I've asked them if
they can provide an early copy so that we can get the packages written
and debugged. Otherwise it will have to be in the Update.
Henry - Please respond to the comments on the
ubuntu-mobile@lists.ubuntu.com mailing list.
Charles Johnson
Ultra-Mobility Group
Platform Software Engineering
Intel Corporation
[EMAIL PROTECTED]
--
Ubuntu-mobile mailing list
Ubuntu-mobile@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
--
Ubuntu-mobile mailing list
Ubuntu-mobile@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
