[Milkymist-devel] Linux boards
Takeshi MATSUYA
macchan at sfc.wide.ad.jp
Sun Sep 6 07:47:57 PDT 2009
Hi,
On 2009/09/06, at 22:51, Sébastien Bourdeauducq wrote:
>> 1. We do not support ECP250.
>> 2. We support ECP250.
>> However, we do not guarantee its working.
>
> I would suggest choice 1 in order to avoid feature creep, and
because we do
> not have a board to test it so that feature will be more or less
dead code.
>
> Also the peripherals (UART and timer) are different between
MicoSystemBuilder
> (MSB) and Milkymist (we do not use LM32UART or LM32TIMER from MSB).
Ok.
ECP250 does not support.
and I changed the driver name.
Boot log is below.
------ log -------
milkymist_uart: registered real console
Dentry cache hash table entries: 262144 (order: 8, 1048576 bytes)
Inode-cache hash table entries: 131072 (order: 7, 524288 bytes)
Memory available: 37248k/65536k RAM, (1344k kernel code, 58k data)
Calibrating delay loop... 158.92 BogoMIPS (lpj=794624)
Mount-cache hash table entries: 512
NET: Registered protocol family 16
checking if image is initramfs...it isn't (bad gzip magic numbers);
looks like an initrd
Freeing initrd mem: 16383k freed
io scheduler noop registered (default)
milkymist_uart: Milkymist UART driver
ttyS0 at I/O 0x0 (irq = 3) is a MILKYMIST_UART
milkymist_uart: added port 0 with irq 3-4 at 0x80000000
RAMDISK driver initialized: 1 RAM disks of 16400K size 1024 blocksize
loop: module loaded
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 16384KiB [1 disk] into ram disk... done.
VFS: Mounted root (ext2 filesystem) readonly.
milkymist_ml401 login:
--------------
Takeshi
More information about the Devel
mailing list