<fluffs> ok, if the only changes are cpu related, then they can be the same id,
the s3c24xx code identifies the cpu for itself
<stefan_schmidt> Hmm, but we have different phones, which also can have
different hw revs
<fluffs> iirc, that is handled by the revision tag being passed through
<stefan_schmidt> fluffs: It's about EZX phones. They use all PXA27x
<stefan_schmidt> fluffs: The differences are for keyboard,gpio, etc..
<fluffs> iirc, the mess that is mach-pxa selects cpu at compile time
<fluffs> if the hardware is different, then that is a good reason for unique
machine IDs
<fluffs> especially if the difference is not detectable at runtime
* stefan_schmidt gets the feeling that pxa is the worst mach type in arm-linux
* fluffs has had to dig in it for a customer, eww
<fluffs> one machine per kernel is not desperately nice
<stefan_schmidt> fluffs: ok, E2 has no TS for example, other has TS only, TS and
flip keyboard...
<stefan_schmidt> fluffs: I have some hope that the earlier models can be used
with a multimachine kernel
<fluffs> the pxa needs work to get it to compile that way
<fluffs> iirc, bits are still #ifdef hell
<fluffs> it is worse than digging in hh.org's cvs
<stefan_schmidt> fluffs: It seems the best way is to work out all the
differences and what is runtime detectable
<fluffs> that sounds like a good plan
<stefan_schmidt> ok, thanks