<br><br><div class="gmail_quote">On Tue, Feb 8, 2011 at 5:47 AM, Andrea Gasparini <span dir="ltr"><<a href="mailto:gaspa@yattaweb.it">gaspa@yattaweb.it</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi,<br>
Working on a custom arm based board, I'm currently juggling with mach-types<br>
and machine IDs for our ARM boards, but perhaps it came the time to set<br>
them in the right way...<br>
<br>
And moreover, do anyone has a pointer on documentation/articles/somewhat<br>
on how to write a good board-*.c and how (and perhaps when) to handle<br>
platform devices instead of a classical device driver? I'm currently going<br>
by trying, and perhaps it's not the better method to achieve my purposes.<br>
<br></blockquote><div><br>theres also a lot of work going on currently in device-trees,<br>which are splitting config data out from code, into text files.<br><br>googling "linux device tree" found a lot of relevant stuff,<br>
there was also a recent LWN.net article on them.<br>Looking at linux-next tree is also useful, there are a bunch of configs<br>for a bunch of arm boards in there.<br><br>good luck<br></div></div>