From: Wu Zhangjin <wuzhangjin@gmail.com>
To: Arnaud Patard <apatard@mandriva.com>
Cc: linux-mips@linux-mips.org, ralf@linux-mips.org,
Yan Hua <yanh@lemote.com>, Philippe Vachon <philippe@cowpig.ca>,
Zhang Le <r0bertz@gentoo.org>, Zhang Fuxin <zhangfx@lemote.com>,
loongson-dev <loongson-dev@googlegroups.com>,
Liu Junliang <liujl@lemote.com>, Erwan Lerale <erwan@thiscow.com>
Subject: Re: [loongson-PATCH-v3 17/25] add a machtype kernel command line argument
Date: Fri, 05 Jun 2009 00:04:33 +0800 [thread overview]
Message-ID: <1244131473.32116.17.camel@falcon> (raw)
In-Reply-To: <m3iqjcm7jd.fsf@anduin.mandriva.com>
On Thu, 2009-06-04 at 15:51 +0200, Arnaud Patard wrote:
> wuzhangjin@gmail.com writes:
>
> Hi,
>
> > From: Wu Zhangjin <wuzj@lemote.com>
> >
> > the difference between yeeloong-7inch and yeeloong-8.9inch is very
> > small, only including the screen size and shutdown logic. so, it's very
> > important to share the same kernel image file between them instead of
> > adding some new kernel config options. benefit from this, the
> > distribution developers only have a need to compile the kernel one time.
> >
> > to share the same kernel image file between yeelooong-7inch and
> > yeeloong-8.9inch, there is a need to add a kernel command line, here I
> > name is machtype, it works like this:
> >
> > machtype=lemote-yeeloong-2f-7inch
> > company - product - cpu revision - size
>
> I'm curious. Why can't you use the boot monitor to pass the right
> machine type instead ? iirc, you're using pmon and pmon has a variable
> called "systype". If the systype variable is not designed for that, I'll
> be happy to know its use :)
>
yes, I just checked the PMON variables, there is "systype" there, but
seems can not be set(when reboot, will become the original one), maybe
hard-coded in PMON? so i added another PMON variable: machtype, and
added some source code: if there is a PMON machtype variable there,
transfer it to a kernel command line.
but i think using a kernel command line is better, because we can either
set it as the karg variable in PMON or pass it in the boot.cfg, which is
more flexible and in-dependent from the bootloader.
and perhaps, someday, we can share the same kernel image file between
fuloong2f box and yeeloong2f laptop via this kernel command line:
machtype, because there is really only a few difference between
them(only the reboot/shutdown logic, serial port). I really want to
share them and remove one of the irq.c file :-)
thanks!
Wu Zhangjin
>
> Arnaud
next prev parent reply other threads:[~2009-06-04 16:04 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1244120575.git.wuzj@lemote.com>
2009-06-04 13:03 ` [loongson-PATCH-v3 04/25] change the naming methods wuzhangjin
2009-06-04 13:04 ` [loongson-PATCH-v3 05/25] remove reference to bonito64.h wuzhangjin
2009-06-04 13:04 ` [loongson-PATCH-v3 06/25] divide the files to the smallest logic unit wuzhangjin
2009-06-04 13:04 ` [loongson-PATCH-v3 07/25] replace tons of magic numbers by understandable symbols wuzhangjin
2009-06-04 13:05 ` [loongson-PATCH-v3 08/25] clean up the early printk support for fuloong(2e) wuzhangjin
2009-06-04 13:05 ` [loongson-PATCH-v3 09/25] enable Real Time Clock Support " wuzhangjin
2009-06-04 13:05 ` [loongson-PATCH-v3 10/25] split the loongson-specific part out wuzhangjin
2009-06-09 17:51 ` Zhang Le
2009-06-10 12:39 ` Wu Zhangjin
2009-06-04 13:06 ` [loongson-PATCH-v3 11/25] split env out of cmdline.c wuzhangjin
2009-06-04 13:06 ` [loongson-PATCH-v3 12/25] add basic loongson-2f support wuzhangjin
2009-06-04 13:06 ` [loongson-PATCH-v3 13/25] add basic fuloong(2f) support wuzhangjin
2009-06-04 13:07 ` [loongson-PATCH-v3 14/25] enable serial port support of loongson-based machines wuzhangjin
2009-06-04 13:07 ` [loongson-PATCH-v3 15/25] add basic yeeloong(2f) laptop support wuzhangjin
2009-06-09 17:23 ` Zhang Le
2009-06-10 12:37 ` Wu Zhangjin
2009-06-04 13:07 ` [loongson-PATCH-v3 16/25] enable halt command for yeeloong-7inch laptop wuzhangjin
2009-06-04 13:08 ` [loongson-PATCH-v3 17/25] add a machtype kernel command line argument wuzhangjin
2009-06-04 13:51 ` Arnaud Patard
2009-06-04 16:04 ` Wu Zhangjin [this message]
2009-06-10 15:40 ` Zhang Le
2009-06-10 20:31 ` [loongson-dev] " Zhang Le
2009-06-11 11:09 ` Zhang Le
2009-06-11 15:16 ` Wu Zhangjin
2009-06-11 14:28 ` Wu Zhangjin
2009-06-04 13:08 ` [loongson-PATCH-v3 18/25] Add Siliconmotion 712 framebuffer driver wuzhangjin
2009-06-04 17:18 ` Simon Braunschmidt
2009-06-04 13:09 ` [loongson-PATCH-v3 19/25] define Loongson2F arch specific phys prot access wuzhangjin
2009-06-04 13:09 ` [loongson-PATCH-v3 20/25] Loongson2 specific OProfile driver wuzhangjin
2009-06-04 13:10 ` [loongson-PATCH-v3 21/25] flush posted write to irq wuzhangjin
2009-06-04 13:10 ` [loongson-PATCH-v3 22/25] CS5536 MFGPT as system clock source support wuzhangjin
2009-06-04 13:10 ` [loongson-PATCH-v3 23/25] Loongson2F cpufreq support wuzhangjin
2009-06-04 13:11 ` [loongson-PATCH-v3 24/25] add gcc 4.4 support for MIPS and loongson wuzhangjin
2009-06-04 13:11 ` [loongson-PATCH-v3 25/25] add default kernel config file for loongson-based machines wuzhangjin
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=1244131473.32116.17.camel@falcon \
--to=wuzhangjin@gmail.com \
--cc=apatard@mandriva.com \
--cc=erwan@thiscow.com \
--cc=linux-mips@linux-mips.org \
--cc=liujl@lemote.com \
--cc=loongson-dev@googlegroups.com \
--cc=philippe@cowpig.ca \
--cc=r0bertz@gentoo.org \
--cc=ralf@linux-mips.org \
--cc=yanh@lemote.com \
--cc=zhangfx@lemote.com \
/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.