I had a look mainly on the register settings for the Samsung CPUs S3C2xx0 a=
nd=20
compared it to the S3C4510 and as far as I see, this is quite different :-(.

Before I really try to porting this cpu to netbsd, I would like to have som=
e=20
more information on the interfaces, the kernel needs. So I will get a glimp=
s=20
of how much effort a port will take.

So what I really need to know is:

1) hardware <-> cpu-specific code <-> netbsd-kernelcode=20
How is the "cpu-specific code" defined? Is there any Documentation availabl=
e=20
about that?
I believe this code will handle things like startup, interrupt, consol for=
=20
kernel output (?) ... (as the s3c2xx0 guys defining something like that)

2) MMU, TLB, Cache, etc -functions are only depending on the arm type=20
(ARM7TDMI in my case)?

3) Where can I find some good arm assembler documentation? As my knowledge =
is=20
very poor and it's based on a i386 architecture :-(

Thanks and Regards - J=F6rn

Am Montag, 6. September 2004 16:26 schrieben Sie:
> On Mon, 2004-09-06 at 15:03, J=F6rn Seger wrote:
> > Some additions:
> >
> > 1) The CPU is based on the ARM7TDMI design
> >
> > 2) When I grep arround in the code, I found some CPU_ARM7TDMI define
> > areas in "arm/cpufunc.*". So I believe CPU/MMU and TLB is basicly
> > supported. Am I right?
> >
> > My questions:
> > Would it just be the addition of
> > options	CPU_ARM7TDMI
> > in the kernel config to add the CPU-support?
>
> It should be, but I can't off-hand see a committed port that uses this
> CPU, so can't give any guarantee that it works correctly.
>
> > On what port should I base this addition?
>
> A (very) quick glance at the product guide for the chip suggests it
> *might* be similar to the evbarm configs for Sumsung's arm9 devices,
> based on the S3C2XXX, so the SMDK2410 and SMDK2800 might prove to be a
> good starting point.
>
> R.