public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Steven Scholz <steven.scholz@imc-berlin.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] CONFIG_SERIAL_TAG and CONFIG_REVISION_TAG ???
Date: Fri, 11 Mar 2005 14:40:57 +0100	[thread overview]
Message-ID: <42319FE9.4060505@imc-berlin.de> (raw)

Hi there,

for ARM boards CONFIG_SERIAL_TAG and CONFIG_REVISION_TAG can be used to pass the 
board's serial nummber and revision to a linux kernel.

For now setup_serial_tag() has to be defined in board specific files. But 
setup_revision_tag() is defined in armlinux.c like

void setup_revision_tag(struct tag **in_params)
{
	u32 rev = 0;
#ifdef CONFIG_OMAP2420H4
	u32 get_board_rev(void);

	rev = get_board_rev();
#endif
	params->hdr.tag = ATAG_REVISION;
	params->hdr.size = tag_size (tag_revision);
	params->u.revision.rev = rev;
	params = tag_next (params);
}

I'd love to make this consistent. So either do it like setup_serial_tag() or 
like setup_serial_tag() ...

Since I don't like board specific defines like "#ifdef CONFIG_OMAP2420H4" in 
common files we should move that out.

So the question is:

shell we implement board specific get_board_rev() and get_board_serial() and 
have the params->hdr.* stuff in armlinux.c?

or

shell we implement setup_serial_tag() and setup_serial_tag() in board specific 
files and do the params->hdr.* stuff there?

Comments please.

Thanks,

Steven

             reply	other threads:[~2005-03-11 13:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-11 13:40 Steven Scholz [this message]
2005-04-06 12:40 ` [U-Boot-Users] CONFIG_SERIAL_TAG and CONFIG_REVISION_TAG ??? Steven Scholz

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=42319FE9.4060505@imc-berlin.de \
    --to=steven.scholz@imc-berlin.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