From: alex@digriz.org.uk (Alexander Clouter)
To: linux-arm-kernel@lists.infradead.org
Subject: Bogus machine-type from bootloader
Date: Sat, 25 Dec 2010 11:34:47 +0000 [thread overview]
Message-ID: <nf1hu7-if4.ln1@chipmunk.wormnet.eu> (raw)
In-Reply-To: BF43E57B-EE45-49B1-AE2A-96F8CBFD40FE@gmail.com
Damjan Marion <damjan.marion@gmail.com> wrote:
>
> Is there any "proper" way if fixing bogus machine type sent by
> bootloader (ofcourse except fixing bootloader itself)?
>
Proper no, as the bootloader is the 'proper' way.
The kludge fix that many distro's seem to use (Debian for example):
http://www.digriz.org.uk/ts78xx/booting-woes#unrecognized.2BAC8-unsupported_machine_ID
In short, what it does is get the first two instructions of a booting
kernel to load the correct machine ID into r1. The example there is for
0x0674 (1652), you can adjust it for your own needs.
Cook the kernel, run the 'fixup' script and you should be okay.
Cheers
--
Alexander Clouter
.sigmonster says: Androphobia:
Fear of men.
prev parent reply other threads:[~2010-12-25 11:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-24 11:19 Bogus machine-type from bootloader Damjan Marion
2010-12-24 11:29 ` Russell King - ARM Linux
2010-12-24 13:17 ` Damjan Marion
2010-12-25 11:34 ` Alexander Clouter [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=nf1hu7-if4.ln1@chipmunk.wormnet.eu \
--to=alex@digriz.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/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