public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] BIOS EMULATOR driver
Date: Mon, 26 Mar 2012 15:31:18 +0200	[thread overview]
Message-ID: <201203261531.18334.marex@denx.de> (raw)
In-Reply-To: <20120326130815.09071200265@gemini.denx.de>

Dear Wolfgang Denk,

> Dear Marek Vasut,
> 
> In message <201203261243.19732.marex@denx.de> you wrote:
> > > > I pretty sure because I try compile it without this driver and
> > > > everything seems to be ok.
> > > 
> > > In the given configurations, the BIOS code only gets built when you
> > > the ATI Radeon support is enabled, in which case it is needed.
> > > 
> > > If you don't enable either, then it's fine as well - but then the BIOS
> > > code does not get built anyway.
> > 
> > But we probably want this driver to work, so ...
> 
> I'm not sure what your comment means.
> 
> If you want to use this driver, then enable it in the configuration;
> this will mean the BIOS emulator also gets built and linked, and it
> will be needed to initialize the card's BIOS.
> 
> Everything is fine.  No problems anywhere.

Right. My concern was about:

"I pretty sure because I try compile it without this driver and everything seems 
to be ok."

So that means the board work without this bios emulator driver if the radeon 
driver is disabled? But we want to use the radeon driver, so we need the bios 
emulator stuff.

I think the discussion quite drifted away from the original question, which was 
if the dead code in bios emulator stuff can be simply removed? ... and if it 
really is dead code.

> 
> 
> What exactly was your concern?
> 
> Best regards,
> 
> Wolfgang Denk

Best regards,
Marek Vasut

  reply	other threads:[~2012-03-26 13:31 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-25 17:23 [U-Boot] BIOS EMULATOR driver Viktor Křivák
2012-03-25 18:30 ` Wolfgang Denk
2012-03-25 23:09   ` Viktor Křivák
2012-03-26  5:51     ` Wolfgang Denk
2012-03-26 10:43       ` Marek Vasut
2012-03-26 13:08         ` Wolfgang Denk
2012-03-26 13:31           ` Marek Vasut [this message]
2012-03-26 20:14             ` Wolfgang Denk
2012-03-26 23:06               ` Marek Vasut
2012-03-27  5:18                 ` Viktor Křivák
2012-03-27 17:28                   ` Wolfgang Denk
2012-03-27 17:48                     ` Marek Vasut
2012-03-27 17:51                       ` Timur Tabi
2012-03-27 17:58                         ` Marek Vasut
2012-03-27 17:59                           ` Timur Tabi
2012-03-27 20:11                             ` Marek Vasut
2012-03-27 22:46                               ` Viktor Křivák
2012-03-27 22:56                                 ` Graeme Russ
2012-03-27 23:46                                   ` Marek Vasut
2012-03-27 23:51                                     ` Graeme Russ
2012-03-27 23:56                                       ` Marek Vasut
2012-03-28  0:00                                         ` Graeme Russ
2012-03-28  0:17                                           ` Marek Vasut
2012-03-26 13:47           ` Viktor Křivák
2012-03-26 14:10             ` Anatolij Gustschin
2012-03-26 14:42             ` Timur Tabi
2012-03-26 20:17               ` Wolfgang Denk

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=201203261531.18334.marex@denx.de \
    --to=marek.vasut@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox