public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Tomi Valkeinen <tomi.valkeinen@nokia.com>
Cc: linux-arm-kernel@lists.arm.linux.org.uk, linux-omap@vger.kernel.org
Subject: Re: [PATCH] ARM: Parse ATAG_VIDEOLFB to screen_info
Date: Tue, 25 Nov 2008 22:08:00 +0000	[thread overview]
Message-ID: <20081125220800.GA29020@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1227601063.7197.18.camel@tubuntu>

On Tue, Nov 25, 2008 at 10:17:43AM +0200, Tomi Valkeinen wrote:
> Hi,
> 
> On Mon, 2008-11-24 at 12:12 +0000, ext Russell King - ARM Linux wrote:
> > On Fri, Nov 21, 2008 at 12:25:36PM +0200, Tomi Valkeinen wrote:
> > > Parse ATAG_VIDEOLFB received from bootloader to screen_info struct,
> > > so that video drivers can use the information.
> > 
> > Boot loaders tend to be absolutely diabolical about passing correct
> > information to the kernel, so I really don't want to see such platform
> > specific stuff being passed.  Please put it in the board specific file
> > instead, just like everyone else does.
> 
> I though a general file would be better, because:
> 
> a) the tag contains only generic stuff and it is parsed directly to
> screen_info, which is also generic
> 
> b) ATAG_VIDEOTEXT, which is very similar to ATAG_VIDEOLFB, is parsed in
> setup.c also.
> 
> c) it is not used anywhere currently

I was meaning "don't do it this way at all" - instead, do it like every
other platform does, and keep the framebuffer settings in the platform
specific files.  Don't encode them into the boot loader and pass them
to the kernel.

Boot loaders are fragile and buggy.  No one likes fixing them.  It takes
_years_ to get problems with them fixed.  It may seem like it's a good
idea to pass lots of platform specific data from the boot loader to the
kernel, but it's just not worth the hastle of getting people to fix that
data when it's not 100% correct.

We've seen this many times.  We've seen it with simple things like passing
the machine number to the kernel.  Just don't go there - it's a pain in
the back side and causes years of grief.


      reply	other threads:[~2008-11-25 22:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-21 10:25 [PATCH] ARM: Parse ATAG_VIDEOLFB to screen_info Tomi Valkeinen
2008-11-24 12:12 ` Russell King - ARM Linux
2008-11-25  8:17   ` Tomi Valkeinen
2008-11-25 22:08     ` Russell King - ARM Linux [this message]

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=20081125220800.GA29020@flint.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-omap@vger.kernel.org \
    --cc=tomi.valkeinen@nokia.com \
    /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