Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 10 Nov 1998 01:39:35 +1100
From:      K <hwg@stardreams.dyn.ml.org>
To:        small@FreeBSD.ORG
Subject:   Re: PC/104 and picobsd
Message-ID:  <3.0.3.32.19981110013935.03c879c0@Tasha.STARDreams.org>
In-Reply-To: <3646D0B0.55D997F5@biella.alpcom.it>

next in thread | previous in thread | raw e-mail | index | archive | help
At 12:23 11/9/98 +0100, Cristian Angelini wrote:
>What I need now it's some more information about the use of picobsd in a
>pc/104 environment. I read the info on the Mesa site, but I still lack
>some basic startup hints: what items should I buy to completely develop
>a prototype and so on. Are all the devices implemented on that cards
>(Flash IDE, ethernet,..) completely supported by picobsd ? May I install
>something like PPP on that cards ?

I've also been looking at PC/104 devices and the way I see it is that
they're actually full PCs, just much smaller, and they should behave pretty
much as normal. The specific board I've been looking at is made by Aaeon,
the PCM-5894 

http://www.aaeon.com/pcm5894.htm

The onboard peripherals are pretty much standard, IDE, floppy, serial
ports, parallel ports.. even USB connectors (although I'm sure we won't be
using those for a while yet :) The Ethernet controller is the Realtek
RTL8139, which recently had driver support added thanks to the programming
of Bill Paul. 

There are so many interesting things you could do with PC/104 systems and
mobile power units for vehicles and even aircraft (some markings in the
PC/104 power supply photos I've seen lead me to believe they make aircraft
models), you could concievably build a portable MP3 player which could take
Zip drives, LS120 drives, or CDROMs (after booting off the DiskOnChip ROM
which contains PicoBSD and amp or something similar).. or a micro-router,
or more.. 

What I'm primarily interested in is putting PicoBSD on larger media,
specifically Zips/LS120, something around 100-120MB, it'd take only 2MB of
space and we'd have the rest for whatever we wanted to do.. I'm testing
this out, more information as it comes up. My test rig isn't quite a PC/104
implementation, but all we need is proof of concept, then it can be almost
transparently adapted for that role :) 

Right now I'm having a slight problem building PicoBSD with the latest
sources and a full source tree. I just completed a full source cvsup
moments ago, the problem is still there, apparently. 

An attempt to build the dialup floppy with all the defaults as come
preconfigured in the source, using the build script in the build directory
results in this : 

loading kernel
rearranging symbols
text    data    bss     dec     hex
925696  1716224 99324   2741244 29d3fc

====================== stage1 started =====================
-> Preparing kernel...
-> Preparing MFS filesystem...
bash-2.02# 

The kernel is compiled properly, stage1 starts properly, the preparing MFS
message pops up then the script immediately drops back to the bash prompt.
It didn't use to do this in 0.31, what am I doing wrong, has the build
procedure changed so vastly since I last worked on it? :)



--
K

"Deliver yesterday, code today, think tomorrow."

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?3.0.3.32.19981110013935.03c879c0>