Re: Re: AddADeviceSideUSB howto help!

Well, I know this was probaly pointless to attempt, but I tried placing all of the patch text into one .patch file (yeah...I have no idea what I'm doing) and added it to the proper locations for the IXP4XX-Kernel. (I'm still running 
2.6.16...dunno where u r getting .18?) and ran a make openslug-kernel.  http://rafb.net/paste/results/OZwj0R65.html is the patch file I created and I received this error log:

Importing patch /home/neomatrixjr/slugos-3.10/openembedded/packages/linux/ixp4xx-kernel/2.6.16/kernel-USB-gadget.patch (stored as kernel-USB-gadget.patch)
Applying patch kernel-USB-gadget.patch
(Stripping trailing CRs from patch.)
patching file drivers/usb/gadget/inode.c
/usr/bin/patch: **** malformed patch at line 4: }

Patch kernel-USB-gadget.patch does not apply (enforce with -f)

any suggestions on how to or if it's possible to use this to patch .16?  I think that's what it was intended for anyway.

On 9/29/06, Michael-Luke Jones <mlj28-KWPb1pKIrIJaa/9Udqfwiw@xxxxxxxxxxxxxxxx> wrote:

I've looked at these patches, and while 2.6.18 still won't compile with IXP4xx gadget support, many of the individuals have been included in the 2.6.18 tree.

As far as I can see, the 2 changesets which are not in but are vital for build are those directly concerning the arm architecture (I don't think the person who wrote these patches ever sent the ARM patches to the correct place, i.e. the ARM mailing list).

My problem with integrating these patches and trying to get them sent upstream is this:

http://tinyurl.com/psflm

This patch is going to be included in 2.6.19 and includes clean support for a GPIO pin to control resetting of the device-side USB support. To add proper support for device-side USB we would need to dedicate a GPIO pin to this purpose. However, there is no spare GPIO pin on the NSLU2.

So, for the NSLU2, adding device-side USB is probably always going to remain a hack and I don't think we can cleanly support it in our 'mainline' kernel.

I've enclosed the bits of the diff I think have not been applied but I can't give any guarantees as to whether it will then work.

Sorry to disappoint,

Mike

On 28 Sep 2006, at 17:16, Justin Richeson wrote:

Ok, well, after months of digging arround google, uClinux, NSLU2-Linux and more I am still coming up with some troubles with getting everything to work right.  I can get usb-device in uClinux, but it doesnt have the other features I need.  So I am asking if anyone can take a look a the following patches I ran across and see if they might help, and also help me install them since I do not know how to patch the kernel.

Thanks!

http://www.gatago.com/linux/kernel/18503727.html [PATCH 0/5] usb gadget: patches to support ixp4xx platform
http://www.gatago.com/linux/kernel/18503723.html [PATCH 1/5] usb gadget: update inode.c to support full speed only  udc
http://www.gatago.com/linux/kernel/18503726.html [PATCH 2/5] usb gadget: update pxa2xx_udc.c and arch dependent files  for ixp4xx
http://www.gatago.com/linux/kernel/18503725.html [PATCH 3/5] usb gadget: update pxa2xx_udc.c driver to fully support  IXP4xx platform
http://www.gatago.com/linux/kernel/18503724.html [PATCH 4/5] usb gadget: clean udc.h
http://www.gatago.com/linux/kernel/18503722.html [PATCH 5/5] usb gadget: don't build small version if usbgadgetfs  is selected

On 8/25/06, m. allan noah <anoah-U3wE8S48E2n2fBVCVOL8/A@xxxxxxxxxxxxxxxx > wrote:

you must install other drivers on which it depends first.

allan

On Fri, 25 Aug 2006, Justin Richeson wrote:

> Got it built with usb modules and installed in test mode. I run insmod for
> the g_file_storage.o and it gives:
>
> http://rafb.net/paste/results/aDGgIA31.html
>
> On 8/25/06, m. allan noah <anoah-U3wE8S48E2n2fBVCVOL8/A@xxxxxxxxxxxxxxxx > wrote:
>>
>>
>> notice this line:
>>
>> Kernel command line: console=ttyS0,115200 root=/dev/ram0 initrd=0x00800000
>>
>> that tells the kernel where the ramdisk will be. you loaded it at
>> 0x01000000
>>
>> try loading it at 0x00800000 instead.
>>
>> allan
>>
>>
>> On Fri, 25 Aug 2006, Justin Richeson wrote:
>>
>> > Per Allan's instructions for testing the image:
>> >
>> > http://rafb.net/paste/results/Pa6hgX35.html
>> >
>> > any thoughts?
>> >
>> > everything seems to load alright, but then it can't find the rom?
>> >
>> > On 8/25/06, Justin Richeson <jrnosee-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx <jrnosee%40gmail.com>>
>> wrote:
>> >>
>> >> Steve, I've got a couple of questions on your instructions before I
>> >> attempt as I've read yours and the how to page that allan sent me.
>> >> is:
>> >>
>> >> devio "<<arch/arm/boot/zImage" 'wb 597 . 256/ 255& 0xe3a01c00+,
>> >> 4; wb 255& 0xe3811000+, 4;cp$' >/tftpboot/zImage
>> >> supposed to be run on my build machine or on the slug in redboot? (I'm
>> >> assuming my machine) and do I need anything special installed to do
>> this or
>> >> is it a standard linux command?
>> >> and you've got the load ramdisk.gz set to 0x00800000, but the other
>> >> instructions indicate 0x01000000. What's the difference/significance
>> here.
>> >> I just want to be sure I don't overwrite part of redboot. I don't have
>> >> jtag
>> >> so I CANT screw that up or I'm toast.
>> >> and lastly, which command line did you mean?:
>> >>
>> >> Add something like this to your linux command line
>> >> "root=/dev/ram0 rootfstype=romfs ro initrd=0x00800000,8M init=/bin/sh"
>> >>
>> >> Thanks!
>> >>
>> >>
>> >> On 8/25/06, Steve Bennett <
>> steveb+nslu2-FnKd1amGuKVYp/FP3KkZ9CCwEArCW2h5@xxxxxxxxxxxxxxxx<steveb%2Bnslu2%40riverstone. dyndns.org>>

>> wrote:
>> >> >
>> >> > You might want to try something like this:
>> >> > - Convert the raw zImage into a form that redboot can load.
>> >> > e.g. devio "<<arch/arm/boot/zImage" 'wb 597 . 256/ 255& 0xe3a01c00+,
>> >> > 4; wb 255& 0xe3811000+, 4;cp$' >/tftpboot/zImage
>> >> > - Load the ramdisk.gz from redboot:
>> >> > RedBoot> load -r -v -b 0x00800000 ramdisk.gz
>> >> > - Load the zImage
>> >> > RedBoot> load -r -v -b 0x1d00000 zImage
>> >> > - Execute it
>> >> > RedBoot> go
>> >> >
>> >> > Of course you will need to:
>> >> > - Make sure your kernel has support for the filesystem you use for
>> your
>> >> > ramdisk (e.g. romfs, cramfs, ext2)
>> >> > - Ensure you have initrd support compiled in
>> >> > - Add something like this to your linux command line
>> >> > "root=/dev/ram0 rootfstype=romfs ro initrd=0x00800000,8M
>> init=/bin/sh"
>> >> >
>> >> > Cheers,
>> >> > Steve
>> >> >
>> >> >
>> >> > Justin Richeson wrote:
>> >> > >
>> >> > >
>> >> > > Well, I managed to get uClinux to build and I have a zImage file
>> and a
>> >> >
>> >> > > ramdisk.gz. Your instructions say to load this from redboot. I do
>> know
>> >> >
>> >> > > how to get into redboot, and I've looked for instructions on
>> loading
>> >> > > uClinux to the NSLU2, but I can't find any specific instructions
>> that
>> >> > > work. I'm only really familiar with loading an .img or .bin file
>> with
>> >> > > upslug2 or SerComm's tool. When I try and load the uncompressed
>> >> > ramdisk
>> >> > > (from ramdisk.gz) it fails. I've tried that as an image and tried
>> it
>> >> > as
>> >> > > a jffs2 and ramdisk with zImage as the kernel. they all fail. How
>> did
>> >> > > you do this allan?
>> >> > >
>> >> > > Thanks!
>> >> >
>> >> > >
>> >>
>> >>
>> >
>>
>> --
>> "so don't tell us it can't be done, putting down what you don't know.
>> money isn't our god, integrity will free our souls" - Max Cavalera
>>
>>
>

--
"so don't tell us it can't be done, putting down what you don't know.
money isn't our god, integrity will free our souls" - Max Cavalera

__._,_.___

SPONSORED LINKS

Door hardware	Decorative hardware	Cabinet hardware
Computer hardware	Window hardware

Your email settings: Individual Email|Traditional
Change settings via the Web (Yahoo! ID required)
Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured
Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe

__,_._,___