From: Matthew Lear <matt@bubblegen.co.uk>
To: u-boot@lists.denx.de
Subject: [U-Boot] Providing more board info from U-Boot to resident OS
Date: Tue, 07 Jul 2009 11:24:17 +0100 [thread overview]
Message-ID: <4A532251.8090906@bubblegen.co.uk> (raw)
Hello all,
U-Boot provides data containing board information to a resident OS that
may be booted. Are there plans to extend this so that an additional
'level' of more specific board information can be provided to the OS?
Specifically, and for example, is there a mechanism that U-Boot can use
to inform the OS (Linux in this case) that it has enabled the watchdog
on the cpu?
Granted, U-Boot and the OS are separate entities up to a point, ie some
kernel arch set up implementations make reference to (or rather, copy)
data structures in u-boot.h (eg Freescale Coldfire).
However, for custom hardware and/or applications there are definite
cases where there is the requirement for more board specific knowledge
to be shared between U-Boot and OS.
Is there a way to do this?
Feedback much appreciated.
Thanks,
-- Matt
next reply other threads:[~2009-07-07 10:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 10:24 Matthew Lear [this message]
2009-07-07 11:36 ` [U-Boot] Providing more board info from U-Boot to resident OS 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=4A532251.8090906@bubblegen.co.uk \
--to=matt@bubblegen.co.uk \
--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