All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4] board support patch for phyCORE-MPC5200B-tiny
Date: Mon, 30 Mar 2009 13:09:30 -0400	[thread overview]
Message-ID: <9e4733910903301009h4373cdb7y82d872b9285a6e18@mail.gmail.com> (raw)
In-Reply-To: <49D0EF8F.7050002@denx.de>

On Mon, Mar 30, 2009 at 12:13 PM, Anatolij Gustschin <agust@denx.de> wrote:
> Jon Smirl wrote:
>> On Sun, Mar 29, 2009 at 10:08 AM, Markus Rathgeb
>> <maggu2810@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

  parent reply	other threads:[~2009-03-30 17:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-24 15:56 [U-Boot] [PATCH v4] board support patch for phyCORE-MPC5200B-tiny Jon Smirl
2009-03-25 19:14 ` Jon Smirl
2009-03-27 20:12   ` Wolfgang Denk
2009-03-27 20:48     ` Jon Smirl
2009-03-29 14:08       ` Markus Rathgeb
2009-03-29 14:29         ` Jon Smirl
2009-03-29 14:39           ` Markus Rathgeb
2009-03-30 16:13           ` Anatolij Gustschin
2009-03-30 17:01             ` Jon Smirl
2009-03-30 17:07               ` Markus Rathgeb
2009-03-30 17:09             ` Jon Smirl [this message]
2009-04-01 18:51               ` Markus Rathgeb
2009-04-01 20:18                 ` Anatolij Gustschin
2009-06-01 18:51 [U-Boot] [PATCH V4] " Jon Smirl
2009-06-05 12:09 ` Jon Smirl
2009-06-08 11:01 ` Jon Smirl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9e4733910903301009h4373cdb7y82d872b9285a6e18@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.