From: George G. Davis <davis_g@comcast.net>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] pass custom data to Linux
Date: Fri, 14 Nov 2003 17:05:16 -0500 [thread overview]
Message-ID: <3FB5519C.9000700@comcast.net> (raw)
In-Reply-To: <fc.004c4e48001e675c004c4e48001e648f.1e677c@rea.de>
Anders Larsen wrote:
> "George G. Davis" <davis_g@comcast.net> schreibt:
>
>>Anders Larsen wrote:
>>
>>>Specifically, I need to pass the board revision and serial number to
>>>the Linux kernel, and I'd like to use the standard method of passing
>>>tagged parameters. For my purpose, ATAG_SERIAL and ATAG_REVISION are
>>>already defined (and supported by the kernel).
>>
>>Since you say you are using standard ARM Linux tags to do this, why not
>>just add support for CONFIG_{REVISION,SERIAL}_TAG in lib_arm/armlinux.c?
>
>
> Hi George,
>
> the tags are standard, but by nature the information is board-specific,
> so I don't see how lib_arm/armlinux.c could do much more than simply
> calling a function from the board tree.
> Do you think my idea of adding the hook setup_custom_tags() is _too_
> generic?
Perhaps we can use environment variables to initialise those common
tags in armlinux.c. Those environment variable can then be uniquely
initialised/defined in whatever way makes sense for a given target
port?
--
Regards,
George
>
> Cheers
> Anders
>
>
next prev parent reply other threads:[~2003-11-14 22:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-12 17:07 [U-Boot-Users] [PATCH] pass custom data to Linux Anders Larsen
2003-11-12 18:14 ` George G. Davis
2003-11-13 8:53 ` Anders Larsen
2003-11-14 22:05 ` George G. Davis [this message]
2003-11-17 8:25 ` Anders Larsen
2003-11-17 9:04 ` Wolfgang Denk
2003-11-17 9:22 ` Anders Larsen
2003-11-17 9:33 ` Wolfgang Denk
2003-11-17 11:10 ` Anders Larsen
2003-11-17 15:12 ` Wolfgang Denk
2003-11-18 9:09 ` Anders Larsen
2003-12-07 0:07 ` Wolfgang Denk
2003-12-07 17:07 ` Anders Larsen
2003-12-08 10:38 ` Anders Larsen
2004-01-02 15:04 ` 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=3FB5519C.9000700@comcast.net \
--to=davis_g@comcast.net \
--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.