public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Multiple device support - none at all?
Date: Thu, 12 Mar 2009 16:25:25 +0100	[thread overview]
Message-ID: <m2tz5yg3ve.fsf@ohwell.denx.de> (raw)
In-Reply-To: <Pine.LNX.4.64ksi.0903101416290.26401@home-gw.koi8.net> (ksi@koi8.net's message of "Tue, 10 Mar 2009 14:30:42 -0700 (PDT)")

Hi ksi (was it Sergei?),

>> The fundamental concept of u-boot isn't to handle all your devices, it is to
>> boot linux (or other OS) and use the OS to handle the multiple devices.
>
> The same is true for a PC BIOS, but it DOES handle all of my devices. And it
> allows me to choose which device to boot from. And it is extendable so I can
> add a PCI card with e.g. RAID controller and boot off of that RAID. And it
> is not handling of all devices, it is _BASIC_ functionality...

Actually I don't know what you're talking about in the PC BIOS area
here.  Usually the computers I own cannot boot from the devices that are
bought somewhat after the motherboard.  But maybe you have different
instances of computers...

> I don't mind reconfiguring and rebuilding the thing for my parcticular
> configuration instead of just changing some settings in interactive setup
> utility, but the current implementation won't allow even that...

Actually we are thinking about "going generic" here also for a while
already.  Look for example at the BOF session notes of OLS 2007[1]
"Device Tree Run Time Configuration".

We are all aware that a "proper" device model will be needed at a
certain stage, only nobody started into that direction yet.

As Jerry pointed out - booting embedded hardware used to be a comparably
simple operation ;)

Cheers
  Detlev

[1] http://www.denx.de/wiki/view/U-Boot/OLSUbootBOF

-- 
... that every year or so they're going to give you a new release full
of 50 000  additional lines of code all  written  by monkeys.  Because
they generally follow  the  ``million monkeys typing,   and eventually
they'll come up with something useful'' school of system development.
	                                    -- Richard M. Stallman
--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de

  reply	other threads:[~2009-03-12 15:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-10 20:41 [U-Boot] Multiple device support - none at all? ksi at koi8.net
2009-03-10 21:15 ` Jerry Van Baren
2009-03-10 21:30   ` ksi at koi8.net
2009-03-12 15:25     ` Detlev Zundel [this message]
2009-03-12 16:00       ` ksi at koi8.net
2009-03-12 17:25         ` Detlev Zundel
2009-03-12 18:07           ` ksi at koi8.net
2009-03-12 19:01             ` Wolfgang Denk
2009-03-12 19:57               ` ksi at koi8.net
2009-03-12 21:29                 ` Wolfgang Denk
2009-03-12 22:11                   ` ksi at koi8.net
2009-03-13  8:24                     ` Heiko Schocher
2009-03-13  6:45             ` Heiko Schocher

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=m2tz5yg3ve.fsf@ohwell.denx.de \
    --to=dzu@denx.de \
    --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