grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: ARM kernel parameters
Date: Sun, 22 Dec 2013 00:45:22 +0100	[thread overview]
Message-ID: <52B62812.2020405@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1032 bytes --]

Hello, all. I've been able to boot Linux on my raspberry pi, after
fixing several bugs in loader. But for this I had to have a line like:
linux /kernel_cutdown.img dma.dmachans=0x???? bcm2708_fb.fbwidth=656
bcm2708_fb.fbheight=416 bcm2708.boardrev=0xe bcm2708.serial=0x????????
smsc95xx.macaddr=??:??:??:??:?? dwc_otg.lpm_enable=0
console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1
root=/dev/mmcblk0p2 rootfstype=ext4 rootwait

When using standard bootloader the part
dma.dmachans=0x???? bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416
bcm2708.boardrev=0xe bcm2708.serial=0x????????
smsc95xx.macaddr=??:??:??:??:??
is added automatically. The part
dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200
console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait
comes from cmdline.txt.

It's not possible to tell for sure then one ends and the other starts.
Does anyone see any problem with prepending the arguments GRUB itself
received to the kernel command line on all platforms using ATAGs?


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 291 bytes --]

             reply	other threads:[~2013-12-21 23:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-21 23:45 Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2013-12-22 19:41 ` ARM kernel parameters Leif Lindholm
2013-12-22 20:58   ` Vladimir 'φ-coder/phcoder' Serbinenko

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=52B62812.2020405@gmail.com \
    --to=phcoder@gmail.com \
    --cc=grub-devel@gnu.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;
as well as URLs for NNTP newsgroup(s).