68000 patches (Atari ST platform)

68000 patches (Atari ST platform)

[Matthias Reis]

Hi all,

today I finally got my hands on the user interrupts for plain 68000 CPUs and it was quite straightforward, just as you have suggested: I implemented user*_inthandlers in entry_mm.S that push the vectornumber onto the stack. My kernel still doesn't boot completely, but it runs now correctly calibrate delay loop (0.59 BogoMIPS, isn't it great? ;) since the timer interrupt is working.

According to the "release early, release often"-mantra, I want now to send some patches to the list. Do you want to have the Atari bootstrap patches in this mailinglist? I'm asking because bootstrap is not (anymore) part of the kernel sources... The next question would be whether you want to have a single head.S version for the Atari ST-nommu platform or a merge with the current arch/m68k/kernel/head.S. The head.S I use does not use much code from the "classic" head.S and is for sure easier to read due to its small size.

Best regards,
Matthias

Re: 68000 patches (Atari ST platform)

[Michael Schmitz]

Hi Matthias,

On Mon, Sep 12, 2011 at 11:09 AM, Matthias Reis
<matthias.reis@physik.tu-berlin.de> wrote:
> Hi all,
>
> today I finally got my hands on the user interrupts for plain 68000 CPUs and it was quite straightforward, just as you have suggested: I implemented user*_inthandlers in entry_mm.S that push the vectornumber onto the stack. My kernel still doesn't boot completely, but it runs now correctly calibrate delay loop (0.59 BogoMIPS, isn't it great? ;) since the timer interrupt is working.

0.6 BogoMIPS sounds about right :-)

> According to the "release early, release often"-mantra, I want now to send some patches to the list. Do you want to have the Atari bootstrap patches in this mailinglist? I'm asking because bootstrap is not (anymore) part of the kernel sources... The next question would be whether you want to have a single head.S version for the Atari ST-nommu platform or a merge with the current arch/m68k/kernel/head.S. The head.S I use does not use much code from the "classic" head.S and is for sure easier to read due to its small size.

Regarding the bootstrap patches - do send them to the list, please.
Whoever does build ataboot binaries occasionally these days can then
pick up your patches.

ataboot used to be part of the m68k CVS on kullervo.debian.net but we
have had to take kullervo offline half a year ago. Christian has
rebuilt the system but we're still having trouble with the ethernet
driver in 3.1 (sort of working on this). I'm sure we can clone the
m68k CVS off kullervo and set it up somewhere else.

My preference would be to have a separate head.S if they cannot be
trivially merged. Your call, or Geert's really though.

Cheers,

  Michael

Re: 68000 patches (Atari ST platform)

[Thorsten Glaser]

Michael Schmitz <schmitzmic <at> googlemail.com> writes:

> ataboot used to be part of the m68k CVS on kullervo.debian.net but we
> have had to take kullervo offline half a year ago. Christian has
> rebuilt the system but we're still having trouble with the ethernet
> driver in 3.1 (sort of working on this). I'm sure we can clone the
> m68k CVS off kullervo and set it up somewhere else.

Ah, there they are ;) I’ve NMU’d the m68k bootstraps (Atari, Amiga, VMS,
Mac except where shared with macppc) in Debian to get their source uploaded
to unreleased (since they were removed from unstable), and wondered about
them. (And the packaging is positively ancient, understandably.)

I could host them (I love CVS, after all, *and* I maintain CVS in Debian,
and use it a lot in BSD…) if you want, and can arrange for commit access
for selected people (tell me whom, and I need a PGP trust path) including
mails (with or (default) without diffs sent inline). I can put it on my
box at home (P-233MMX with an actual Hercules Graphics Card, behind ADSL)
or put a separate repo on another box, whatever is your preference.

bye,
//mirabilos

Re: 68000 patches (Atari ST platform)

[Geert Uytterhoeven]

On Thu, Sep 15, 2011 at 13:45, Thorsten Glaser <tg@mirbsd.de> wrote:
> Michael Schmitz <schmitzmic <at> googlemail.com> writes:
>
>> ataboot used to be part of the m68k CVS on kullervo.debian.net but we
>> have had to take kullervo offline half a year ago. Christian has
>> rebuilt the system but we're still having trouble with the ethernet
>> driver in 3.1 (sort of working on this). I'm sure we can clone the
>> m68k CVS off kullervo and set it up somewhere else.
>
> Ah, there they are ;) I’ve NMU’d the m68k bootstraps (Atari, Amiga, VMS,
> Mac except where shared with macppc) in Debian to get their source uploaded
> to unreleased (since they were removed from unstable), and wondered about
> them. (And the packaging is positively ancient, understandably.)
>
> I could host them (I love CVS, after all, *and* I maintain CVS in Debian,
> and use it a lot in BSD…) if you want, and can arrange for commit access
> for selected people (tell me whom, and I need a PGP trust path) including
> mails (with or (default) without diffs sent inline). I can put it on my
> box at home (P-233MMX with an actual Hercules Graphics Card, behind ADSL)
> or put a separate repo on another box, whatever is your preference.

I think I have a git clone at home...

Gr{oetje,eeting}s,

                        Geert - no - more - CVS

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

Re: 68000 patches (Atari ST platform)

[Michael Schmitz]

Hi Thorsten,

>
> Ah, there they are ;) I’ve NMU’d the m68k bootstraps (Atari, Amiga, VMS,

I don't think VMS was m68k based :-) VME is what we have.

> Mac except where shared with macppc) in Debian to get their source uploaded
> to unreleased (since they were removed from unstable), and wondered about
> them. (And the packaging is positively ancient, understandably.)

The code doesn't change very fast if at all so the packaging doesn't
need to. Actually there was one thing I wanted to try with ataboot:
make it report the FastRAM chunk before the ST-RAM one if we were to
place the kernel in FastRAM. Never got the cross compiler setup sorted
out.

> I could host them (I love CVS, after all, *and* I maintain CVS in Debian,
> and use it a lot in BSD…) if you want, and can arrange for commit access
> for selected people (tell me whom, and I need a PGP trust path) including
> mails (with or (default) without diffs sent inline). I can put it on my
> box at home (P-233MMX with an actual Hercules Graphics Card, behind ADSL)
> or put a separate repo on another box, whatever is your preference.

Geert has a git clone of the repo so it could be either CVS or git. I
don't mind either way - a home box would be OK, we just need to make
sure cvs.linux-m68k points that way.

Cheers,

  Michael

Re: 68000 patches (Atari ST platform)

[Thorsten Glaser]

Michael Schmitz dixit:

>> Ah, there they are ;) I�ve NMU�d the m68k bootstraps (Atari, Amiga, VMS,
>
>I don't think VMS was m68k based :-) VME is what we have.

Yeah, obvious typo ☺

>The code doesn't change very fast if at all so the packaging doesn't
>need to.

Debian changes, though… not much, and not fast, but it does.

>place the kernel in FastRAM. Never got the cross compiler setup sorted
>out.

Maybe this helps?
	deb https://www.freewrt.org/~tg/debs68k/ cross main

That one contains binutils, gcc-4.4, eglibc and linux-libc-dev stuff
for cross-compiling from sid/amd64 to sid/m68k.

>Geert has a git clone of the repo so it could be either CVS or git. I
>don't mind either way - a home box would be OK, we just need to make
>sure cvs.linux-m68k points that way.

I can do CVS if I get a dump of the repo (i.e. the ,v files), but
won’t touch that git thingy ;-) I don’t mind either way. Just an
offer.

bye,
//mirabilos
-- 
13:22⎜«neurodamage» mira, what's up man? I have a CVS question for you in #cvs
13:22⎜«neurodamage» since you're so good w. it │ «neurodamage:#cvs» i love you
13:28⎜«neurodamage:#cvs» you're a handy guy to have around for systems stuff ☺
16:06⎜<Draget:#cvs> Thank god I found you =)   20:03│«bioe007:#cvs» mira2k: ty
17:14⎜<ldiain:#cvs> Thanks big help you are :-)   <bioe007> mira|nwt: ty again
18:35⎜«alturiak:#cvs» mirabilos: aw, nice. thanks :o
18:36⎜«ThunderChicken:#cvs» mirabilos FTW!  23:03⎜«mithraic:#cvs» aaah. thanks
18:41⎜«alturiak:#cvs» phew. thanks a bunch, guys. you just made my weekend :-)
18:10⎜«sumit:#cvs» mirabilos: oh ok.. thanks for that
21:57⎜<bhuey:#cvs> yeah, I really appreciate help
18:50⎜«grndlvl:#cvs» thankyou            18:50⎜«grndlvl:#cvs» worked perfectly
20:50⎜<paolo:#cvs> i see. mirabilos, thnks for your support
00:36⎜«halirutan:#cvs» ok, the obvious way:-) thx
18:44⎜«arcfide:#cvs» mirabilos, I am running OpenBSD.     18:59⎜«arcfide:#cvs»
Hrm, yes, I see what you mean. 19:01⎜«arcfide:#cvs» Yeah, thanks for the help.
21:33⎜«CardinalFang:#cvs» Ugh.  Okay.  Sorry for the dumb question.  Thank you
21:34⎜<centosian:#cvs> mirabilos: whoa that's sweet
21:52⎜«garrett__:#cvs» much appreciated  «garrett__:#cvs» thanks for your time
23:39⎜<symons:#cvs> this worked, thank you very much 16:26⎜<schweizer:#cvs> ok
thx, i'll try that     20:00⎜«stableable:#cvs» Thank you.    20:50⎜«s833:#cvs»
mirabilos: thanks a lot.        19:34⎜<bobbytek:#cvs> Thanks for confirming :)
20:08⎜<tsolox:#cvs> ...works like a charm.. thanks mirabilos