All of lore.kernel.org
 help / color / mirror / Atom feed
From: marek.vasut@gmail.com (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: machine definition for colibri-pxa3xx
Date: Thu, 8 Jul 2010 14:06:19 +0200	[thread overview]
Message-ID: <201007081406.20038.marek.vasut@gmail.com> (raw)
In-Reply-To: <201007081236.39550.pieterg@gmx.com>

Dne ?t 8. ?ervence 2010 12:36:39 pieterg napsal(a):
> At the moment, colibri-pxa300.c as well as colibri-pxa320.c have their own
> machine definition.
> 
> However, running a kernel built with CONFIG_MACH_COLIBRI300 and
> CONFIG_MACH_COLIBRI320 on a colibri 300 or 310, it will match the 320
> machine definition, and therefore use colibri-pxa320.c.

Huh? Your bootloader is messed up? What bootloader do you use ?
> 
> I believe it's not possible to differentiate colibri pxa3xx based on
> machine definitions, but only by checking the their cpu.
> 
> Wouldn't it make sense to place a single "Toradex Colibri PXA3xx" machine
> definition in colibri-pxa3xx.c, and use cpu_is_pxa3nn to do cpu specific
> initialisation?
> This is exactly how things are done for zylonite by the way.
> 
> I have some colibri pxa310 patches, but we need a working machine detection
> before they will actually do anything.
> 
> Rgds, Pieter
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2010-07-08 12:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-08 10:36 machine definition for colibri-pxa3xx pieterg
2010-07-08 12:06 ` Marek Vasut [this message]
2010-07-08 12:55   ` pieterg
2010-07-08 15:18     ` Marek Vasut
2010-07-08 15:59       ` pieterg
2010-07-08 20:07         ` Marek Vasut

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=201007081406.20038.marek.vasut@gmail.com \
    --to=marek.vasut@gmail.com \
    --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 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.