u-boot and x-loader patch for 500 MPU and 166 DDR

GoogleGroups
1

Hi all,

Here, is a patch for u-boot and x-loader to get 500MPU and 166 DDR working for beagle. It is against the current version on code.google.com.

Regards,

Khasim

u-boot_500mpu_166ddr.patch (1.58 KB)

x-load_500mpu_166ddr.patch (4.5 KB)

2

Thanks Khasim.

I rebuilt u-boot and x-load today and verified that /proc/cpuinfo
shows 499.92 BogoMIPS. I also have rebuilt the kernel to not have the
L2 cache disable box checked.

For u-boot, your patches didn't cleanly apply against denx.de 1.3.2
with the earlier Beagle u-boot patches. There are some spaces on the
line that weren't in your version. I applied the patch by hand.

For x-load, the patch applied fine, but the x-load doesn't build as it
is distributed by code.google.com. I had to add links to a couple of
header files in u-boot. This has been mentioned on the mailing list
before, but it isn't included in your building instructions.

I'm using the kernel from code.google.com, not the linux-omap git, but
I have added many drivers and turned off the L2 cache disable. It
seems to be looking healthy, other than some occasional USB EHCI port
device resets that we are working to get to the bottom of.

-Jason

3

Thanks Khasim.

I rebuilt u-boot and x-load today and verified that /proc/cpuinfo
shows 499.92 BogoMIPS. I also have rebuilt the kernel to not have the
L2 cache disable box checked.

For u-boot, your patches didn’t cleanly apply against denx.de 1.3.2
with the earlier Beagle u-boot patches. There are some spaces on the
line that weren’t in your version. I applied the patch by hand.

This patch is against our version 1.1.4 on code.google.com.

For x-load, the patch applied fine, but the x-load doesn’t build as it
is distributed by code.google.com. I had to add links to a couple of
header files in u-boot. This has been mentioned on the mailing list
before, but it isn’t included in your building instructions.

I don’t add any links, will have to check this out. What are the header files that is affecting us here?

I’m using the kernel from code.google.com, not the linux-omap git, but
I have added many drivers and turned off the L2 cache disable. It
seems to be looking healthy, other than some occasional USB EHCI port
device resets that we are working to get to the bottom of.

Yes, I am porting all drivers to latest GIT, I will move USB to 2.6.25 it should have some fixes for HUB don’t know if it directly helps to fix our issue.

Regards,
Khasim