Subject: Re: L2 CACHE
To: Tim Kelly <hockey@dialectronics.com>
From: Bill Studenmund <wrstuden@netbsd.org>
List: port-macppc
Date: 12/20/2004 19:17:05
--r7U+bLA8boMOj+mD
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Dec 06, 2004 at 12:43:58PM -0500, Tim Kelly wrote:
> At 12:41 PM -0500 12/6/04, Brian Hechinger wrote:
> >well, here is what i have in my config file:
> >
> >options	L2CR_CONFIG=3D"(L2SIZ_1M|L2CLK_20|L2RAM_PIPELINE_BURST|L2CR_L2WT)
>=20
> I see a leading " in the option. It's supposed to be a long integer, so if
> it gets interpreted as an array of chars, no telling what it does :-)

I realize this thread's a bit old, but I wanted to follow up.

Note that this text is in the kernel config option. The quote (with=20
trailing quote that wasn't pasted) tell config that L2CR_CONFIG should be=
=20
that one specific string. This quoting ensures that the config file=20
parsing code doesn't attempt to understand the parenthesis and the pipe=20
symbols.

This option turns into the following line in opt_ppcparam.h:

#define  L2CR_CONFIG     (L2SIZ_1M|L2CLK_20|L2RAM_PIPELINE_BURST|L2CR_L2WT)

Thus by the time the C compiler is involved, this will turn into an=20
integer. :-)

Take care,

Bill

--r7U+bLA8boMOj+mD
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFBx5WxWz+3JHUci9cRAoemAJ0b0bk40VJrvWAm90QwRezrmayq6ACeLNPG
m4Y7f1luemlv6AqUaAuEAvM=
=p8fr
-----END PGP SIGNATURE-----

--r7U+bLA8boMOj+mD--