linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
* machine definition for colibri-pxa3xx
@ 2010-07-08 10:36 pieterg
  2010-07-08 12:06 ` Marek Vasut
  0 siblings, 1 reply; 6+ messages in thread
From: pieterg @ 2010-07-08 10:36 UTC (permalink / raw)
  To: linux-arm-kernel

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.

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2010-07-08 20:07 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-07-08 10:36 machine definition for colibri-pxa3xx pieterg
2010-07-08 12:06 ` Marek Vasut
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

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).