Date: Mon, 18 Dec 2000 14:19:02 -0700 From: Warner Losh <imp@village.org> To: "Michael C . Wu" <keichii@peorth.iteration.net> Cc: Devin Butterfield <dbutter@wireless.net>, freebsd-small@FreeBSD.ORG, Jordan Hubbard <jkh@winston.osd.bsdi.com>, freebsd-hackers@FreeBSD.ORG Subject: Re: StrongARM support? Message-ID: <200012182119.OAA94431@harmony.village.org> In-Reply-To: Your message of "Mon, 18 Dec 2000 15:12:35 CST." <20001218151235.D69041@peorth.iteration.net> References: <20001218151235.D69041@peorth.iteration.net> <78656.976769151@winston.osd.bsdi.com> <3A3862E4.5A46E14C@wireless.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20001218151235.D69041@peorth.iteration.net> "Michael C
. Wu" writes:
: IIRC, NetBSD doesn't have the newer StrongARM SA-11xx ports.
: And that's why we have to work from ARM/Linux.
In conversations that I had with an unnamed vendor a while ago, the
newer parts should be just a few days of casual effort to incorporate
into NetBSD. The glue chips for the eval boards likely would be more
work, but the mods for the new CPU would be farily minimal.
: With PicoBSD not working very well in -CURRENT and the advent of
: large sized flash media (SANDISK/CompactFlash, SmartMedia).
: Can we begin to maybe have a "make buildsmallworld" target?
: (i.e. a combination of NO_STATIC=yes and other suitable options)
Maybe. I have a script that will effectively do a installsmallworld
target. The guts of the script are a for loop that does
(cd $FreeBSDSrcDir
make -m ${FreeBSDSrcDir}/share/mk -f Makefile.inc1 \
hierarchy DESTDIR=$1 NOMAN=yes
(cd etc ; make -m ${FreeBSDSrcDir}/share/mk \
distribution DESTDIR=$1 NOMAN=yes)
for i in ${FreeBSDProgramDirs}; do
echo "==> $i"
test -d $i &&
(cd $i ; make -m ${FreeBSDSrcDir}/share/mk \
install -DNOINFO -DNOMAN DESTDIR=$1 -DNOPROFILE)
done)
which lets you tweak things to year heart's delight. Every time I go
to put this script up, I run into the "oh, but I want it to do X Y and
Z before posting." problem. Maybe I should just post it.
: In addition, -CURRENT has become very much larger. I know about
: the "embedded systems are customized, so cut it down yourself"
: argument. However, what if it's still large after we cut it down
: to the bare minimum? Also, what about /dev/random seeding problems?
There are lots of ways to seed /dev/random in an embdeeded system.
Warner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-small" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200012182119.OAA94431>