U-boot recent comments feed

AmigaOneG3SE code same as for XE/MicroA1

Mon, 10 May 2010 17:11:09 +0200

Issue: uboot AmigaOneG3SE sources do not compile in Denx ELDK kit
Author: billt
It appears that the boards/MAI/AmigaOneG3SE drawer is used for all Eyetech AmigaOne machines, despite the G3SE name. I presume that the XE and MicroA1 are also compiled from this same code.

This is a general cascading PCI-to-PCI bridge issue

Sat, 13 Jun 2009 08:07:15 +0200

Issue: PCI-Express bridge/switch scanning
Author: hans
I just tried plugging in a Radeon HD 2400 card into the 66 MHz PCI slot on the A1-XE. The 66 MHz PCI slot is behind a bridge already, so as a result the HD 2400 chipset is behind two cascaded bridges, i.e.:

CPU <-> Artica-S PCI-PCI bridge (66 MHz) <-> PLX PCI-PCIe bridge <-> RV610 chipset (Radeon HD 2400 pro)

Ranger shows that UBoot detects the PLX bridge chip, but then initializes it as if it were a card (even gives it an IRQ line); it never detects the presence of the RV610 chipset.

bridge on bridge

Tue, 05 May 2009 21:48:02 +0200

Issue: PCI-Express bridge/switch scanning
Author: billt
This may be a bridge on bridge issue, as a PCI-Express switch should appear as a bridge to software such as uboot.

A1XE <-> PEX8111 bridge <-> PEX8618 switch(bridge) <-> SiI3132, Realtek 8111b, Jmicron JMB363, PCIe graphics, etc.

This is with the 8111 plugged into a PCI-33MHz slot on the A1XE. I have not tried with the 66MHz PCI slot.

Oh... not sure if i was clear enough there.

Wed, 01 Oct 2008 09:30:09 +0200

Issue: Catweasel Mk3 keyboard doesn't work if set as default
Author: Xeron
I meant so say, if you save it as default *and then reboot* it stops working. It only works if you set it at the commandline using a PS/2 keyboard, it switches over OK, but when you boot with it set to catweasel as default it just doesn't work.

New variable ps2_init

Tue, 30 Sep 2008 22:39:49 +0200

Issue: PS/2 Keyboard init
Author: Rogue
I invented a new variable ps2_init with the following values

"always" - Always initialize the PS/2 keyboard. The default
"never" - Never initialize the PS/2 keyboard. Handle with care
"auto" - Automatically determine if a PS/2 init is required. If there is a USB or catweasel keyboard already found during startup, PS/2 init is skipped.

Possible solutions

Mon, 29 Sep 2008 12:28:19 +0200

Issue: Wireless USB keyboards might not be recognized.
Author: Rogue
A possible solution might be to issue an (optional) second USB reset later in the boot process, hoping that by that time the device has settled correctly.

Anybody with this issue, can you try to issue a "usb reset" from the prompt and see whether this cures the problem?