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

* machine definition for colibri-pxa3xx
  2010-07-08 10:36 machine definition for colibri-pxa3xx pieterg
@ 2010-07-08 12:06 ` Marek Vasut
  2010-07-08 12:55   ` pieterg
  0 siblings, 1 reply; 6+ messages in thread
From: Marek Vasut @ 2010-07-08 12:06 UTC (permalink / raw)
  To: linux-arm-kernel

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

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

* machine definition for colibri-pxa3xx
  2010-07-08 12:06 ` Marek Vasut
@ 2010-07-08 12:55   ` pieterg
  2010-07-08 15:18     ` Marek Vasut
  0 siblings, 1 reply; 6+ messages in thread
From: pieterg @ 2010-07-08 12:55 UTC (permalink / raw)
  To: linux-arm-kernel

On Thursday 08 July 2010 14:06:19 Marek Vasut wrote:
> 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 ?

Perhaps? I'm using u-boot.

Actually, I now see what you mean.

gd->bd->bi_arch_number = MACH_TYPE_COLIBRI320;

that causes it.
My bootloader (modified 1.3.3) is from before MACH_TYPE_COLIBRI300 was 
added.

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

* machine definition for colibri-pxa3xx
  2010-07-08 12:55   ` pieterg
@ 2010-07-08 15:18     ` Marek Vasut
  2010-07-08 15:59       ` pieterg
  0 siblings, 1 reply; 6+ messages in thread
From: Marek Vasut @ 2010-07-08 15:18 UTC (permalink / raw)
  To: linux-arm-kernel

Dne ?t 8. ?ervence 2010 14:55:16 pieterg napsal(a):
> On Thursday 08 July 2010 14:06:19 Marek Vasut wrote:
> > 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 ?
> 
> Perhaps? I'm using u-boot.
> 
> Actually, I now see what you mean.
> 
> gd->bd->bi_arch_number = MACH_TYPE_COLIBRI320;
> 
> that causes it.
> My bootloader (modified 1.3.3) is from before MACH_TYPE_COLIBRI300 was
> added.

http://openpxa.sourceforge.net , you might want to try it ;-) There is actually 
a stable release and there are some more nice additions in GIT.

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

* machine definition for colibri-pxa3xx
  2010-07-08 15:18     ` Marek Vasut
@ 2010-07-08 15:59       ` pieterg
  2010-07-08 20:07         ` Marek Vasut
  0 siblings, 1 reply; 6+ messages in thread
From: pieterg @ 2010-07-08 15:59 UTC (permalink / raw)
  To: linux-arm-kernel

On Thursday 08 July 2010 17:18:02 Marek Vasut wrote:
> http://openpxa.sourceforge.net , you might want to try it ;-) There is
> actually a stable release and there are some more nice additions in GIT.

Nice progress.
When I started with the pxa3xx you weren't that far yet with your IPL. I now 
have a bootloader which does all I need (show splash screen, read i2c 
eeprom, load kernel from nand, boot).
But I'd like to give your IPL a try, see if it is faster than the modded 
nand_spl that I ended up using ;)

Rgds, Pieter

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

* machine definition for colibri-pxa3xx
  2010-07-08 15:59       ` pieterg
@ 2010-07-08 20:07         ` Marek Vasut
  0 siblings, 0 replies; 6+ messages in thread
From: Marek Vasut @ 2010-07-08 20:07 UTC (permalink / raw)
  To: linux-arm-kernel

Dne ?t 8. ?ervence 2010 17:59:36 pieterg napsal(a):
> On Thursday 08 July 2010 17:18:02 Marek Vasut wrote:
> > http://openpxa.sourceforge.net , you might want to try it ;-) There is
> > actually a stable release and there are some more nice additions in GIT.
> 
> Nice progress.
> When I started with the pxa3xx you weren't that far yet with your IPL. I
> now have a bootloader which does all I need (show splash screen, read i2c
> eeprom, load kernel from nand, boot).
> But I'd like to give your IPL a try, see if it is faster than the modded
> nand_spl that I ended up using ;)
> 
> Rgds, Pieter

The GIT version is tuned for speed (the CPU doesn't run on the lowest frequency 
anymore as in the release version).

How to compile that GIT version you can find on the website. You'll need both U-
Boot and OBM2 from GIT for that though!

btw. I recall you being quite dissatisfied with the old OpenPXA version, but I 
hope it moved further now :) And hey, developers are welcome, it's still one man 
show so it takes time to make some progress :(

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