<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
ron minnich wrote:
<blockquote
cite="mid:13426df10806041112t19ed94b6sab9b99924dcac3c2@mail.gmail.com"
type="cite">
<pre wrap="">On Wed, Jun 4, 2008 at 11:10 AM, Stefan Reinauer <a class="moz-txt-link-rfc2396E" href="mailto:stepan@coresystems.de"><stepan@coresystems.de></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I'm not against using structs, in fact maybe we should just do it, but
they're not the optimal solution either. The guy who invented struct was
not a firmware developer</pre>
</blockquote>
<pre wrap=""><!---->
you gotta trust me on this, but, back then, writing an OS was not that
much different. In fact Unix V6 and coreboot are just about the same
size ...
</pre>
</blockquote>
So are you saying we should make this part of our coding guidelines? <br>
<br>
I believe we really have not used this anywhere in v2 so far. Maybe we
should start doing this for v3?<br>
<br>
How do we handle tables like the resource setup in the K8 code? It's
mostly int arrays of<br>
<br>
{ <br>
offset, andvalue, orvalue, <br>
offset, andvalue, orvalue, <br>
offset, andvalue, orvalue, <br>
}<br>
<br>
This kind of partial filling would have to be done in code completely<br>
<br>
mystruct.member1 &= andvalue1;<br>
mystruct.member1 |= orvalue1;<br>
...<br>
<br>
Or is there a better way?<br>
<br>
<br>
<pre class="moz-signature" cols="72">--
coresystems GmbH • Brahmsstr. 16 • D-79104 Freiburg i. Br.
Tel.: +49 761 7668825 • Fax: +49 761 7664613
Email: <a class="moz-txt-link-abbreviated" href="mailto:info@coresystems.de">info@coresystems.de</a> • <a class="moz-txt-link-freetext" href="http://www.coresystems.de/">http://www.coresystems.de/</a>
Registergericht: Amtsgericht Freiburg • HRB 7656
Geschäftsführer: Stefan Reinauer • Ust-IdNr.: DE245674866
</pre>
</body>
</html>