[U-Boot] [PATCH v4] board support patch for phyCORE-MPC5200B-tiny

[Markus Rathgeb]

An undocumented register? Are the specifications not released for the
series <= r700? But I have to confess to never read the specifications
of ATI/AMD.

Have you found something?

Are you able to try to build pcm030_config with a recent checkout?

=============
make -C drivers/rtc/
make[1]: Entering directory
`/home/maggu2810/phytec/u-boot/u-boot.git_20090401/drivers/rtc'
make[1]: Leaving directory
`/home/maggu2810/phytec/u-boot/u-boot.git_20090401/drivers/rtc'
make[1]: Entering directory
`/home/maggu2810/phytec/u-boot/u-boot.git_20090401/drivers/rtc'
powerpc-603e-linux-gnu-gcc -g  -Os   -fPIC -ffixed-r14 -meabi
-D__KERNEL__ -DTEXT_BASE=0xFFF00000
-I/home/maggu2810/phytec/u-boot/u-boot.git_20090401/include
-fno-builtin -ffreestanding -nostdinc -isystem
/home/maggu2810/phytec/OSELAS.Toolchain-1.99.3/powerpc-603e-linux-gnu/gcc-4.3.2-glibc-2.8-binutils-2.18-kernel-2.6.27-sanitized/lib/gcc/powerpc-603e-linux-gnu/4.3.2/include
-pipe  -DCONFIG_PPC -D__powerpc__ -DCONFIG_MPC5xxx -ffixed-r2 -mstring
-mcpu=603e -mmultiple -DTEXT_BASE=0xFFF00000
-I/home/maggu2810/phytec/u-boot/u-boot.git_20090401/board -Wall
-Wstrict-prototypes -fno-stack-protector -c -o date.o date.c
powerpc-603e-linux-gnu-gcc -g  -Os   -fPIC -ffixed-r14 -meabi
-D__KERNEL__ -DTEXT_BASE=0xFFF00000
-I/home/maggu2810/phytec/u-boot/u-boot.git_20090401/include
-fno-builtin -ffreestanding -nostdinc -isystem
/home/maggu2810/phytec/OSELAS.Toolchain-1.99.3/powerpc-603e-linux-gnu/gcc-4.3.2-glibc-2.8-binutils-2.18-kernel-2.6.27-sanitized/lib/gcc/powerpc-603e-linux-gnu/4.3.2/include
-pipe  -DCONFIG_PPC -D__powerpc__ -DCONFIG_MPC5xxx -ffixed-r2 -mstring
-mcpu=603e -mmultiple -DTEXT_BASE=0xFFF00000
-I/home/maggu2810/phytec/u-boot/u-boot.git_20090401/board -Wall
-Wstrict-prototypes -fno-stack-protector -c -o pcf8563.o pcf8563.c
pcf8563.c:37: error: static declaration of 'rtc_read' follows
non-static declaration
/home/maggu2810/phytec/u-boot/u-boot.git_20090401/include/rtc.h:64:
error: previous declaration of 'rtc_read' was here
pcf8563.c:38: error: static declaration of 'rtc_write' follows
non-static declaration
/home/maggu2810/phytec/u-boot/u-boot.git_20090401/include/rtc.h:65:
error: previous declaration of 'rtc_write' was here
make[1]: *** [pcf8563.o] Error 1
make[1]: Leaving directory
`/home/maggu2810/phytec/u-boot/u-boot.git_20090401/drivers/rtc'
make: *** [drivers/rtc/librtc.a] Error 2
=============


On Mon, Mar 30, 2009 at 7:09 PM, Jon Smirl <jonsmirl at gmail.com> wrote:
> On Mon, Mar 30, 2009 at 12:13 PM, Anatolij Gustschin <agust at denx.de> wrote:
>> Jon Smirl wrote:
>>> On Sun, Mar 29, 2009 at 10:08 AM, Markus Rathgeb
>>> <maggu2810 at googlemail.com> wrote:
>>>> Hi!
>>>>
>>>> Have you read the BIOSEMU stuff in the mailing list?
>>>> Can you adjust the PCI section and perhaps you can include the video
>>>> example (set undef video).
>>>
>>> I have v1 of the pcm030 hardware and the baseboard doesn't have a PCI slot.
>>>
>>> I looked at some of your older emails. It looks like the framebuffer
>>> is not accessible. You are hanging on a write to the PCI bus.
>>>
>>> Forget about running the video BIOS initially, just use the memory
>>> commands from u-boot to make sure you can read and write the
>>> framebuffer.
>>
>> No, memory access to frame buffer will only work after the SD-RAM
>> controller of the GPU is properly initialized. Video BIOS is supposed
>> to do this among other things. As the boot log showed, video memory
>> size was not recognized by the radeon driver which indicates that
>
> That comment triggered a memory. There is a bug fix in the fbdev
> Radeon driver in Linux that pokes an undocumented register. That poke
> fixes this problem. The problem is only present one some cards, not
> all. It is a flaw in the ASIC.
>
> I'm looking at the the fbdev driver but I can't remember where the fix is.
>
>> the video BIOS run failed to initialize the graphic chip and memory
>> controller. Fixing the XLB Initiator Window configuration for bus
>> PCI IO space starting at 0x00000000 seemed to solve problems with
>> video BIOS run.
>>
>> Best regards,
>> Anatolij
>>
>>
>
>
>
> --
> Jon Smirl
> jonsmirl at gmail.com
>