headers
Tim Rightnour | 22 Jun 2007 17:27
Gravatar

NOTICE: major changes to ofppc incoming


A complete rewrite of the ofppc port has been committed to the
ppcoea-rennovation branch as of yesterday.  This rewrite will significantly
change how the port works in general, and there are some caveats that go with
this. Rationale for the change is at the bottom of this email.

1) The port is now more like other ppc ports, where we interface with the
hardware directly, rather than performing all IO/etc through the OFW builtin
drivers.  The OFW is now used to locate and setup devices, which we talk to via
the standard MI devices in NetBSD.

2) The port probably does not run on any machines as of today.  I believe that
it will be relatively straightforward to fix up the port to run on a number of
different machines that have been port targets for ofppc.  The amount of work
required to get the port running on those machines should now be much much less
than it would have been before.

I believe the IBM 7043-150 or 7046-B50 would be the easiest target to get the
new ofppc running on.  At a minimum, I suspect there would need to be some
fiddling with the console, bus_space, and isa code to get it to single user.

Other machines, like the pegasos, or efika, will be slightly more difficult,
but I feel that is primarily due to the interrupt controllers on those devices.

If anyone decides they would like to take a crack at porting ofppc to a
machine, and needs assistance understanding some of the code, I will be more
than glad to assist as much as I can.

Rationale for this change:
(Continue reading)

Permalink | Reply | 47 comments |
headers
Frank Wille | 22 Jun 2007 18:13
Picon

Re: NOTICE: major changes to ofppc incoming

Tim Rightnour wrote:

> A complete rewrite of the ofppc port has been committed to the
> ppcoea-rennovation branch as of yesterday.
> [...]
> 1) The port is now more like other ppc ports, where we interface with the
> hardware directly, rather than performing all IO/etc through the OFW
> builtin drivers. The OFW is now used to locate and setup devices, which we
> talk to via the standard MI devices in NetBSD.

That's great! Thanks a lot for your effort. It is much appreciated!

> Other machines, like the pegasos, or efika, will be slightly more
> difficult, but I feel that is primarily due to the interrupt controllers
> on those devices.
> 
> If anyone decides they would like to take a crack at porting ofppc to a
> machine, and needs assistance understanding some of the code, I will be
> more than glad to assist as much as I can.

What is the exact name of the branch tag? I would like to check it out and
play with it a bit.

Unfortunately my holidays have nearly ended now, but when I got enough time
and reach something useful for Pegasos or Efika I will contact you. :)

--

-- 
    _  Frank Wille (frank <at> phoenix.owl.de)
 _ //  http://sun.hasenbraten.de/~frank/
 \X/   Phx  <at>  #AmigaGer
(Continue reading)

Permalink | Reply | 45 comments |
headers
Tim Rightnour | 23 Jun 2007 08:13
Gravatar

Re: NOTICE: major changes to ofppc incoming


On 22-Jun-2007 Frank Wille wrote:
>> ppcoea-rennovation branch as of yesterday.
>> [...]
> 
> What is the exact name of the branch tag? I would like to check it out and
> play with it a bit.

ppcoea-renovation.  Just like above, but spelled right.  :)

---
Tim Rightnour <root <at> garbled.net>
NetBSD: Free multi-architecture OS http://www.netbsd.org/
Genecys: Open Source 3D MMORPG: http://www.genecys.org/
Permalink | Reply | 43 comments |
headers
Frank Wille | 23 Jun 2007 15:53
Picon

Re: NOTICE: major changes to ofppc incoming

Tim Rightnour wrote:

On 23.06.07 06:13:02 you wrote:

> On 22-Jun-2007 Frank Wille wrote:
>> What is the exact name of the branch tag? I would like to check it out
>> and play with it a bit.
> 
> ppcoea-renovation.  Just like above, but spelled right.  :)

Ok. Got it! :)

Hm. Any chance to have a look onto Jorge Acereda's modifications for
SmartFirmware and trying to include them?

At the moment I don't get any output at all. Even after setting the
kernel-base and textaddr to 0x400000 and including the SmartFirmware fix in
powerpc/powerpc/oea/ofw_subr.S (do not disable address-translation for SF).

I might debug it this weekend some more. Unfortunately I cannot remember all
of Jorge's patches.

--

-- 
    _  Frank Wille (frank <at> phoenix.owl.de)
 _ //  http://sun.hasenbraten.de/~frank/
 \X/   Phx  <at>  #AmigaGer
Permalink | Reply | 41 comments |
headers
Tim Rightnour | 23 Jun 2007 17:25
Gravatar

Re: NOTICE: major changes to ofppc incoming

On 23-Jun-2007 Frank Wille wrote:
> Hm. Any chance to have a look onto Jorge Acereda's modifications for
> SmartFirmware and trying to include them?

Hrmm.. I'm not aware of those.. got a link?

> At the moment I don't get any output at all. Even after setting the
> kernel-base and textaddr to 0x400000 and including the SmartFirmware fix in
> powerpc/powerpc/oea/ofw_subr.S (do not disable address-translation for SF).

No output from anything, or just after the bootloader runs, no output?  What
device is this on?

Maybe try to throw printfs in the very early stages of
arch/powerpc/oea/ofwoea_machdep.c:ofwoea_initppc() and see if any fire.  There
were some changes made to that file to make macppc work, and it's possible that
they are interfering.

---
Tim Rightnour <root <at> garbled.net>
NetBSD: Free multi-architecture OS http://www.netbsd.org/
Genecys: Open Source 3D MMORPG: http://www.genecys.org/
Permalink | Reply | 40 comments |
headers
Jochen Kunz | 26 Jun 2007 23:17
Picon

Re: NOTICE: major changes to ofppc incoming

On Sat, 23 Jun 2007 08:25:24 -0700 (MST)
Tim Rightnour <root <at> garbled.net> wrote:

> > Hm. Any chance to have a look onto Jorge Acereda's modifications for
> > SmartFirmware and trying to include them?
> Hrmm.. I'm not aware of those.. got a link?
Have a look at the mail from Jorge to this list:
Subject: Pegasos patches
Date: Mon, 31 Jul 2006 00:08:31 +0200

> > At the moment I don't get any output at all. Even after setting the
> > kernel-base and textaddr to 0x400000 and including the SmartFirmware
> > fix in powerpc/powerpc/oea/ofw_subr.S (do not disable
> > address-translation for SF).
> No output from anything, or just after the bootloader runs, no output?
>  What device is this on?
I tried with an EFIKA a few minutes ago. The last thing I get is:
Using IP address: 192.168.1.103
root addr=192.168.1.2 path=/nfsroot/NetBSD/ofppc
2715948+223740 [160768+156767]=0x31b754
 start=0x100000

I put some printf(9) in intppc() and ofwoea_initppc() but don't get
anything from them.
--

-- 

tschüß,
       Jochen

Homepage: http://www.unixag-kl.fh-kl.de/~jkunz/
(Continue reading)

Permalink | Reply | 39 comments |
headers
..I'd rather be coding ASM! | 27 Jun 2007 00:51
Picon

Re: NOTICE: major changes to ofppc incoming


Where's your console set to dump?

On Tue, 26 Jun 2007, Jochen Kunz wrote:

> On Sat, 23 Jun 2007 08:25:24 -0700 (MST)
> Tim Rightnour <root <at> garbled.net> wrote:
>
>>> Hm. Any chance to have a look onto Jorge Acereda's modifications for
>>> SmartFirmware and trying to include them?
>> Hrmm.. I'm not aware of those.. got a link?
> Have a look at the mail from Jorge to this list:
> Subject: Pegasos patches
> Date: Mon, 31 Jul 2006 00:08:31 +0200
>
>>> At the moment I don't get any output at all. Even after setting the
>>> kernel-base and textaddr to 0x400000 and including the SmartFirmware
>>> fix in powerpc/powerpc/oea/ofw_subr.S (do not disable
>>> address-translation for SF).
>> No output from anything, or just after the bootloader runs, no output?
>>  What device is this on?
> I tried with an EFIKA a few minutes ago. The last thing I get is:
> Using IP address: 192.168.1.103
> root addr=192.168.1.2 path=/nfsroot/NetBSD/ofppc
> 2715948+223740 [160768+156767]=0x31b754
> start=0x100000
>
> I put some printf(9) in intppc() and ofwoea_initppc() but don't get
> anything from them.
>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Matt Sealey | 27 Jun 2007 00:48
Gravatar

Re: NOTICE: major changes to ofppc incoming

Two quick questions

1) where do I get this tree quickly and easily (I'm loathe to guess through
cvs/svn documentation, I always seem to miss something if it's not written
in "cvs for dummies" like sourceforge has)

2) does it crosscompile? I don't have any way of building a powerpc system
from anything but a linux x86 laptop at the moment. the last time I tried
this the suggestion (from the FreeBSD team I got the same result) was for
me to buy a cheap old Mac to get the first stuff built. That's really beyond
my means and the Efika will be all I have to do any further builds (not
using it for builds means I can do more work)

--

-- 
Matt Sealey <matt <at> genesi-usa.com>
Genesi, Manager, Developer Relations

Jochen Kunz wrote:
> On Sat, 23 Jun 2007 08:25:24 -0700 (MST)
> Tim Rightnour <root <at> garbled.net> wrote:
> 
>>> Hm. Any chance to have a look onto Jorge Acereda's modifications for
>>> SmartFirmware and trying to include them?
>> Hrmm.. I'm not aware of those.. got a link?
> Have a look at the mail from Jorge to this list:
> Subject: Pegasos patches
> Date: Mon, 31 Jul 2006 00:08:31 +0200
> 
>>> At the moment I don't get any output at all. Even after setting the
>>> kernel-base and textaddr to 0x400000 and including the SmartFirmware
(Continue reading)

Permalink | Reply | 10 comments |
headers
..I'd rather be coding ASM! | 27 Jun 2007 02:56
Picon

Re: NOTICE: major changes to ofppc incoming


PSIM

On Tue, 26 Jun 2007, Matt Sealey wrote:

> Two quick questions
>
> 1) where do I get this tree quickly and easily (I'm loathe to guess through
> cvs/svn documentation, I always seem to miss something if it's not written
> in "cvs for dummies" like sourceforge has)
>
> 2) does it crosscompile? I don't have any way of building a powerpc system
> from anything but a linux x86 laptop at the moment. the last time I tried
> this the suggestion (from the FreeBSD team I got the same result) was for
> me to buy a cheap old Mac to get the first stuff built. That's really beyond
> my means and the Efika will be all I have to do any further builds (not
> using it for builds means I can do more work)
>
>
Permalink | Reply | 1 comment |
headers
Jochen Kunz | 27 Jun 2007 09:10
Picon

Re: NOTICE: major changes to ofppc incoming

On Wed, 27 Jun 2007 01:51:17 +0300 (EEST)
"..I'd rather be coding ASM!" <uridium <at> deviate.fi> wrote:

> Where's your console set to dump?
You mean serial console?
Yes. I only use serial console for this type of hacking.

But it should not matter. I didn't check the new branch but in the old
code NetBSD uses only OFW calls to do console IO in early stages of
bootup. So the actual console device does not matter.
--

-- 

tschüß,
       Jochen

Homepage: http://www.unixag-kl.fh-kl.de/~jkunz/
Permalink | Reply | 0 comments |

Gmane