Protocol/procedures for new hardware?

Hi all,

Our company has an embedded linux product using the cs89712 chip.  Although 
we've done a lot of things similar to the CDB89712 demo board, ours varies 
from that and has lots of other hardware/peripherals.  As such, i wish to 
create a the capability to select the kernel/driver code changes for this 
hardware from make config (eventually getting useful additions rolled into 
the rmk branch and farther).  I want to make sure that i follow a standard 
way of doing things, and i haven't seen much documentation on taking this 
step.  

on the arm linux pages, under "machines", i see the cs89712 listed as a 
machine (#92), but then it says that the information is for the demo board, 
not for the cs89712 processor, itself.  (and the demoboard information listed 
is not quite right)   Later, the cdb89712 (#107) is listed.  There is also a 
(new?) cs89712-based unit (#118).  When our hardware is ready for primetime, 
i expect to see it take a slot, too.

Through what hoops must i jump in order to put everything in order such that 
i can release a patch to the world at large and have everybody happy with it? 
 (that is, recognized)  At some point do i request an architecture number?  
Does the naming of compilation/config macros (eg. CONFIG_CDB89712, as already 
exists) follow any specific convention?  etc etc etc.

Before we even have one of these commercially advertised, let alone going out 
the door, we already have tons of interest from universities.  I want to make 
sure everything is done right so time isn't wasted trying to make it right 
later.

thanks,
cam

_______________________________________________
http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
http://www.arm.linux.org.uk/armlinux/mailinglists.php
Please visit the above addresses for information on this list.