linux-apus-devel

Re: Incoming to hq.fsmlabs.com:/home/bk/linuxppc_2_4

[Geert U. <ge...@li...>]

On Mon, 23 Apr 2001, Gabriel Paubert wrote:
> On Mon, 23 Apr 2001, Geert Uytterhoeven wrote:
> > Nothing has to be swapped. Note that this is not PCI.
> 
> Gosh, I would have sweared that I had read that APUS had PCI :-(
> This explains all. Thanks (and now I see that CONFIG_PCI is off for APUS
> of course).

Some boards have some expansion connector that carries PCI signals. You can put
a Permedia2 card on that connector.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li...

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: Incoming to hq.fsmlabs.com:/home/bk/linuxppc_2_4

[Geert U. <ge...@li...>]

On Mon, 23 Apr 2001, Gabriel Paubert wrote:
> On Mon, 23 Apr 2001, Benjamin Herrenschmidt wrote:
> > >In the short term we could either do the pmac_ide_init thing like in
> > >2.2, or we could #define cli() to be ide_cli() in <asm/ide.h> and have
> > >that go through and do disable_irq for all the IDE irqs.
> > 
> > The pmac_ide_init() thing appear to be the "sanest" way to do it.
> > #define'ing cli() looks as hellish as the current workaround ;)
> 
> Indeed.
> 
> > I'm surprised as well that Linus ever accepted our IDE hack that
> > #define insw/outsw & friends in ide.h ... I'm wondering if we can
> > get rid of that or if it's still really useful ? Since we cleaned
> > up our generic insw/outsw functions to not do byteswap, I beleive
> > IDE should be able to use them "as is".
> 
> Yes. BTW how does it work on the APUS, the hardware swaps bytes it seems,
> but either:
> 
> - they don't have IDE (unlikely)

Of course APUS has IDE. It's just an Amiga with a PPC accel card.
Look at drivers/ide/gayle.c for the A1200/4000 builtin IDE.

BTW, there are also IDE expansion cards for Amiga.

> - the IDE controller takes this into account for PIO accesses, and byte
> swapping rules depend on who is the master (ugly)

Nothing has to be swapped. Note that this is not PCI.

> - we need to use the byte-swapping {in,out}s[wl] for IDE on APUS
> 
> - all the disks on APUS are byteswapped (so you can't read a CD) or
> you have to use fancy options.

No problem with disks and CDs. That problem exists on Atari :-)

> - nobody cares anymore about the APUS.

http://linux-apus.sourceforge.net/

> - all of the above :-)

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li...

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

[ linux-apus-Bugs-417987 ] PCMCIA Ethernet + Kernel 2.4.x = false

[<no...@so...>]

Bugs item #417987, was updated on 2001-04-22 04:05
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105907&aid=417987&group_id=5907

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: PCMCIA Ethernet + Kernel 2.4.x = false

Initial Comment:
When trying to use any of the precompiled Linux/APUS
Kernels which are avaible for download from here, the
Kernel just stopps and looks for the Ethernet card.

While using one of the older Kernels (2.2.x),
everything works fine except that I can't use
BlizzPPC-SCSI and Ethernet at the same time.

Here is my dmesg output:

>>>start>>>
Total memory = 63MB; using 0kB for hash table (at 00000000)
Linux version 2.4.2 (michdaen@pismo) (gcc version 2.95.3
20010219 (prerelease)) #66 Thu Mar 15 18:29:35 CET 2001
Amiga hardware found: [A1200] VIDEO BLITTER AUDIO FLOPPY
A1200_IDE KEYBOARD MOUSE SERIAL PARALLEL A2000_CLK CHIP_RAM
PAULA LISA ALICE_PAL PCMCIA ZORRO
On node 0 totalpages: 16256
zone(0): 16256 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/hda3 debug=mem nobat 60nsram
amiga_enable_irq: Trying to enable auto-vector IRQ 1
amiga_enable_irq: Trying to enable auto-vector IRQ 3
amiga_enable_irq: Trying to enable auto-vector IRQ 4
amiga_enable_irq: Trying to enable auto-vector IRQ 5
amiga_enable_irq: Trying to enable auto-vector IRQ 7
amiga_enable_irq: Trying to enable auto-vector IRQ 2
amiga_enable_irq: Trying to enable auto-vector IRQ 6
APUS: BATs=1, BUS=67MHz, RAM=60ns, PCI bridge=0
time_init: decrementer frequency = 16.504254 MHz
Console: colour dummy device 80x25
Calibrating delay loop... 109.77 BogoMIPS
Memory: 61124k available (1688k kernel code, 788k data,
264k
init, 0k highmem)
Dentry-cache hash table entries: 8192 (order: 4, 65536
bytes)
Buffer-cache hash table entries: 1024 (order: 0, 4096
bytes)
Page-cache hash table entries: 16384 (order: 4, 65536
bytes)
Inode-cache hash table entries: 4096 (order: 3, 32768
bytes)
POSIX conformance testing by UNIFIX
PCI: Probing PCI hardware
Zorro: Probing AutoConfig expansion devices: 1 device
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Starting kswapd v1.8
Console: switching to colour frame buffer device 80x25
fb0: Amiga AGA frame buffer device, using 1280K of
video memory
clgen: Driver for Cirrus Logic based graphic boards, v1.9.8
 Couldn't find PCI device
pty: 256 Unix98 ptys configured
block: queued sectors max/low 40496kB/13498kB, 128
slots per
queue
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024
blocksize
loop: enabling 8 loop devices
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 50MHz system bus speed for PIO modes;
override
with idebus=xx
ide0: Gayle IDE interface (A1200 style)
hda: QUANTUM FIREBALL_TM2550A, ATA DISK drive
hdb: QUANTUM FIREBALL1280A, ATA DISK drive
ide0 at 80da0000 on irq 0x0000000c
hda: 5008752 sectors (2564 MB) w/76KiB Cache,
CHS=4969/16/63
hdb: 2503872 sectors (1282 MB) w/83KiB Cache,
CHS=2484/16/63
Partition check:
 hda: RDSK hda1 hda2 hda3
 hdb: RDSK hdb1 hdb2
FD: probing units
found <5>fd: drive 0 didn't identify, setting default
ffffffff
fd0
Looking for PCMCIA ethernet card
:
<<<<end<<<<


I don't know if this helps anything when conserning
about the 2.2.x problem with BlizzPPC-SCSI and Ethernet:

---start---
Date: Sat, 21 Apr 2001 21:19:21 +0200
From: Ignatios Souvatzis <is...@ne...>
To: por...@ne...
Subject: BlizzardPPC scsi, anyone?

Hi,

it was pointed out to me that anything necessary to
build a BlizzardPPC scsi
frontent driver to our siop driver can be deduced from
looking at the Linux
code, especially:


        - Zorro ID are 8512/110 (we knew that), BUT
        - base address is 0xf40000, not the one from
Amiga AutoConfig(tm)
        - interupt line is the "ports" interupt (ipl 2)
        - chip is a 53c710
        - scsi clock is 50 MHz.

If anybody want to make this into a driver (you need
the Amiga siop, not the
siop2), please do -- you can mostly steal the structure
of the cbiiisc, but
using the 53c710 calls and includes (like drscsi.c).

Else, if anybody would run alpha tests, speak up, too.

Regards,
        Ignatios
----end----


----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105907&aid=417987&group_id=5907

Re: CVS Update: 2.3 (branch: trunk)

[Roman Z. <zi...@li...>]

Hi,

> Log message:
>   new dmasound driver by Iain Sandoe
>   minor compile fixes

Ok, guys, you can enjoy your mp3's. :-)

bye, Roman

CVS Update: 2.3 (branch: trunk)

[Roman Z. <zi...@us...>]

CVSROOT:	/cvsroot/linux-apus
Module name:	2.3
Repository:	2.3/drivers/sound/dmasound/
Changes by:	zippel@usw-pr-cvs1.	01/04/21 18:21:13

Log message:
  new dmasound driver by Iain Sandoe
  minor compile fixes

Modified files:
      2.3/drivers/sound/dmasound/:
        dmasound.h dmasound_core.c dmasound_paula.c 
  
  Revision      Changes    Path
  1.2           +58 -37    2.3/drivers/sound/dmasound/dmasound.h
  1.2           +901 -475  2.3/drivers/sound/dmasound/dmasound_core.c
  1.2           +40 -9     2.3/drivers/sound/dmasound/dmasound_paula.c

Re: MOL

[Glenn H. <gh...@c2...>]

Hello Francois

On 20-Apr-2001, you wrote:

> Any progress with this Glenn....I might give this a whirl this weekend
> with the latest kernel release's

I haven't looked at it after this.
I may look some more at it this weekend.
Let us know how it goes if you try it :-)

- glenn


> On Mon, 16 Apr 2001, Glenn Hisdal wrote:

>> Hello 

>> On 16-Apr-2001, Alan wrote:

>>> hi,

>>>> I have now tested this new version of MOL using a 2.4.3 kernel.
>>>> First it complained about unresolved symbol 'find_path_device',
>>>> so I added a find_path_device function that just returned NULL in
>>>> apus_setup.c (after looking at the mol-branch sources).

>>> :-) 
>>> 
>>>> NIP: FFF00544 XER: 20000000 LR: 10002B94 SP: 7FFFFC80 REGS: c5dd9e90
>>>> TRAP: 0200

>> Geert mentioned that itslooking for a ROM in memory...did you tell MOL
>> to use a New World ROM Image , or just ran MOL ?

>> I have configured it to use a new world rom. (in /etc/molrc) I don't have
>> a rom image, so I don't know if it will work with one present, but I was
>> expecting it to complain about a missing rom file when it couldn't find
>> it...

Re: MOL

[Francois P. <fp...@uu...>]

Any progress with this Glenn....I might give this a whirl this weekend
with the latest kernel release's

Francois

On Mon, 16 Apr 2001, Glenn Hisdal wrote:

> Hello 
> 
> On 16-Apr-2001, Alan wrote:
> 
> > hi,
> 
> >> I have now tested this new version of MOL using a 2.4.3 kernel.
> >> First it complained about unresolved symbol 'find_path_device',
> >> so I added a find_path_device function that just returned NULL in
> >> apus_setup.c (after looking at the mol-branch sources).
> 
> > :-) 
> > 
> >> NIP: FFF00544 XER: 20000000 LR: 10002B94 SP: 7FFFFC80 REGS: c5dd9e90
> >> TRAP: 0200
> 
> > Geert mentioned that itslooking for a ROM in memory...did you tell MOL to
> > use a New World ROM Image , or just ran MOL ?
> 
> I have configured it to use a new world rom. (in /etc/molrc)
> I don't have a rom image, so I don't know if it will work with one present,
> but I was expecting it to complain about a missing rom file when it couldn't
> find it...
> 
> 
> - glenn
> 
> 
> 
> _______________________________________________
> Linux-APUS-user mailing list
> Lin...@li...
> http://lists.sourceforge.net/lists/listinfo/linux-apus-user
> 

Re: MOL

[Alan B. <al...@ms...>]

hi,

> I'm currently considering porting MOL to other platforms
> than Linux/PPC (primarily *BSD and Darwin). Before doing that 
> however, I though it might be nice to have it working on APUS.

good idea :-)
 
> - Does the BK kernels at fsmlabs contain working APUS support?

dont know.... BK changes get integrated into the APUS CVS (held at
sourceforge)...i dont think theres a reversal.
 
> - Any special quirks? In particular, why is the kernel
> *not* located at physical address 0?

LinuxAPUS-capable Amigas are of two varieties.... those with 2Mb of
ChipRAM and those with 1Mb of ChipRAM. This ChipRAM is what used to make
the Amiga so very good at its sound and gfx..its memory addressable
directly by the custom chips...and therefore if the CPU has to use it, it
falls into contention...having to wait 2 clockcycles for access.. it also
runs at a slow rate and is of slow speed.  A large chunk of that ChipRAM
is also used by the framebuffer for display (if the Amiga concerned does
not have a gfx card) and for sound (ditto - no sound card installed). 
from memory (no pun intended) its 1.2Mb taken up for custom chip
utilisation on an 'AGA' (2Mb installed) machine.

FastRAM is memory only accessible by the CPU..hence its name. there is no
contention with the cusotm chips, its local to the CPU on the PowerPC
cards and its usually the 60ns flavour. 

memory access speeds (measured under AmigaOS) are something like  ~8Mb/s
for ChipRAM and 40Mb/s upwards (depending on operation) for FastRAM
(604 PowerPC cards on Amigas get around 80Mb/s iirC)

 > - Which cpu flavors are used? MOL currently lacks 603(e) support,

no!!!! argh. when did this drop out? Whilst I was looking at MOL there was
603(e) support...but the kernel required a run-time patching...and hooks
were installed into the kernel to allow this.

 > but I intend to add support for this processor shortly. > 

great! this is what I have.

> To be able to add APUS support, I obviously need help with
> testing and debugging since I don't have an APUS box.

I can help you out...having the required machine AND MacOS CD's lying next
to it.
 
alan

Re: MOL

[Roman Z. <zi...@li...>]

Hi,

Samuel Rydh wrote:

> So... where are the exception vectors on APUS? Are there
> branches from 0xN00 to fastmem? I guess this would imply
> that the kernel image is always in the range of an absolute
> branch (which would simplify things quite a bit).

The IP bit is set in MSR for APUS, so you end up at 0xfff0xx00, from
where we jump back to the kernel. I'm not sure if it's in the 26bit
range, (checking...), nope, the kernel is at 0x8000000.

bye, Roman

Re: MOL

[Samuel R. <sa...@ib...>]

On Thu, Apr 19, 2001 at 10:58:04PM +0200, Roman Zippel wrote:
> Hi,
> 
> Samuel Rydh wrote:
> 
> > - Does the BK kernels at fsmlabs contain working APUS support?
> 
> No, although I started to send Cort patches, but it takes ages... :(
> 
> > - Any special quirks? In particular, why is the kernel
> > *not* located at physical address 0?

The exception vectors then, are they 

> 
> The chipram is already there and it's to slow to be usable for normal
> memory. Patches are available to get the APUS kernel booting 
> with MOL enabled.

Actually, the hooks which used to be present in the 2.4 kernel
are no longer used by MOL. The latest kernel only exports a few
extra symbols. Instead, MOL hooks the very first instruction 
of each exception vector (this makes the low-level code 
system independent).

So... where are the exception vectors on APUS? Are there
branches from 0xN00 to fastmem? I guess this would imply
that the kernel image is always in the range of an absolute
branch (which would simplify things quite a bit).

Cheers,

/Samuel


----------------------------------------------------------
 E-mail <sa...@ib...>  WWW: <http://www.ibrium.se>
  Phone/fax: (home) +46 8 4418431, (work) +46 8 7908470   
----------------------------------------------------------

Re: New AFFS

[Michel <mic...@ii...>]

Roman Zippel wrote:

> > PS: Do you have any idea about the sound bug?
> 
> No, I didn't look at it yet.
> Yesterday I was looking at the parallel port, but without a printer I
> can't really test it. Anyway, I could give some pointers/hints where to
> look, but someone else needs to do some hacking/testing.
> Maybe at the weekend I look into the sound issue, as that I can test
> actually. :)

Great. I think we better wait until that's fixed before putting up new
binaries.


-- 
Earthling Michel Dänzer (MrCooper)    \   Debian GNU/Linux (powerpc) developer
CS student, Free Software enthusiast   \        XFree86 and DRI project member

Re: New AFFS

[Roman Z. <zi...@li...>]

Hi,

"Michel Dänzer" wrote:

> PS: Do you have any idea about the sound bug?

No, I didn't look at it yet.
Yesterday I was looking at the parallel port, but without a printer I
can't really test it. Anyway, I could give some pointers/hints where to
look, but someone else needs to do some hacking/testing.
Maybe at the weekend I look into the sound issue, as that I can test
actually. :)

bye, Roman

Re: new a2232 (Re: CVS Update: 2.3 (branch: trunk))

[Roman Z. <zi...@li...>]

Hi,

"Michel Dänzer" wrote:

> Forgot to add ser_a2232fw.h?

Sorry, fixed now.

bye, Roman

CVS Update: 2.3 (branch: trunk)

[Roman Z. <zi...@us...>]

CVSROOT:	/cvsroot/linux-apus
Module name:	2.3
Repository:	2.3/drivers/char/
Changes by:	zippel@usw-pr-cvs1.	01/04/19 14:38:16

Log message:
  forgot a2232 firmware file

Added files:
      2.3/drivers/char/:
        ser_a2232fw.h 

Re: MOL

[Glenn H. <gh...@c2...>]

Hello 

On 19-Apr-01, Samuel wrote:

> I'm currently considering porting MOL to other platforms
> than Linux/PPC (primarily *BSD and Darwin). Before doing that 
> however, I though it might be nice to have it working on APUS.

That would be great :-)

> To be able to add APUS support, I obviously need help with
> testing and debugging since I don't have an APUS box.

I'll be happy to do some testing :-)


- glenn

new a2232 (Re: CVS Update: 2.3 (branch: trunk))

[Michel <mic...@ii...>]

Roman Zippel wrote:

> Log message:
>   new a2232 version
> 
> Modified files:
>       2.3/drivers/char/:
>         ser_a2232.c ser_a2232.h
> 
>   Revision      Changes    Path
>   1.3           +573 -562  2.3/drivers/char/ser_a2232.c
>   1.2           +133 -429  2.3/drivers/char/ser_a2232.h

This fails:

gcc -D__KERNEL__ -I/home/michdaen/src/apus-cvs/2.4/include -Wall
-Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing
-D__powerpc__ -fsigned-char -msoft-float -pipe -ffixed-r2 -Wno-uninitialized
-mmultiple -mstring    -c -o ser_a2232.o ser_a2232.c
ser_a2232.c:107:  No such file or directory
ser_a2232.c: In function `a2232board_init':
ser_a2232.c:809: `a2232_65EC02code' undeclared (first use in this function)
ser_a2232.c:809: (Each undeclared identifier is reported only once
ser_a2232.c:809: for each function it appears in.)


Forgot to add ser_a2232fw.h?


-- 
Earthling Michel Dänzer (MrCooper)    \   Debian GNU/Linux (powerpc) developer
CS student, Free Software enthusiast   \        XFree86 and DRI project member

Re: MOL

[Roman Z. <zi...@li...>]

Hi,

Samuel Rydh wrote:

> - Does the BK kernels at fsmlabs contain working APUS support?

No, although I started to send Cort patches, but it takes ages... :(

> - Any special quirks? In particular, why is the kernel
> *not* located at physical address 0?

The chipram is already there and it's to slow to be usable for normal
memory.
Patches are available to get the APUS kernel booting with MOL enabled.

> - Which cpu flavors are used? MOL currently lacks 603(e) support,
> but I intend to add support for this processor shortly.

603/604.

bye, Roman

Re: New AFFS

[Michel <mic...@ii...>]

Roman Zippel wrote:

> > Do you consider it stable enough for new binaries?
> 
> Yes, I think so, it's even in Alan's patches now. :-)

No kidding! 8-)


Updating and building...


PS: Do you have any idea about the sound bug?

-- 
Earthling Michel Dänzer (MrCooper)    \   Debian GNU/Linux (powerpc) developer
CS student, Free Software enthusiast   \        XFree86 and DRI project member

Re: New AFFS

[Roman Z. <zi...@li...>]

Hi,

"Michel Dänzer" wrote:

> Do you consider it stable enough for new binaries?

Yes, I think so, it's even in Alan's patches now. :-)

bye, Roman

Re: MOL

[Michel <mic...@ii...>]

Samuel Rydh wrote:
> 
> I'm currently considering porting MOL to other platforms
> than Linux/PPC (primarily *BSD and Darwin).

Time for a name change? ;)

> Before doing that however, I though it might be nice to have it working on
> APUS.

Thanks for thinking of us! :)

> The recent changes to MOL removes almost all assumptions
> about the kernel. As far as I can tell, the only thing that
> prevents MOL from working on APUS systems is the nonstandard
> KERNELBASE stuff.
> 
> So, I have a few questions:
> 
> - Does the BK kernels at fsmlabs contain working APUS support?

I doubt it. Only Jesper Skov used to have BK write permissions but he's been
out of APUS development for about a year. Roman Zippel would be the worthiest
successor, there's been some discussion about that but I don't know if
anything has come out of it yet.

The authoritative source for APUS is our CVS tree where Roman integrates BK
after each minor version bump. The current is 2.4.3.


> - Any special quirks? In particular, why is the kernel
> *not* located at physical address 0?

Because the memory starting at 0 is so-called 'chip memory' shared with the
custom chips and thus very slow. The kernel resides in 'fast memory'.


> - Which cpu flavors are used? MOL currently lacks 603(e) support,
> but I intend to add support for this processor shortly.

We have 603e and 604e so far.


> To be able to add APUS support, I obviously need help with
> testing and debugging since I don't have an APUS box.

We've been constantly hit by questions about when MOL was going to work on
APUS so there should be a lot of people who'd like to test it. :)


-- 
Earthling Michel Dänzer (MrCooper)    \   Debian GNU/Linux (powerpc) developer
CS student, Free Software enthusiast   \        XFree86 and DRI project member

MOL

[Samuel R. <sa...@ib...>]

I'm currently considering porting MOL to other platforms
than Linux/PPC (primarily *BSD and Darwin). Before doing that 
however, I though it might be nice to have it working on APUS.

The recent changes to MOL removes almost all assumptions
about the kernel. As far as I can tell, the only thing that
prevents MOL from working on APUS systems is the nonstandard
KERNELBASE stuff.

So, I have a few questions:

- Does the BK kernels at fsmlabs contain working APUS support?

- Any special quirks? In particular, why is the kernel
*not* located at physical address 0?

- Which cpu flavors are used? MOL currently lacks 603(e) support, 
but I intend to add support for this processor shortly.

To be able to add APUS support, I obviously need help with
testing and debugging since I don't have an APUS box.


Regards,

/Samuel


----------------------------------------------------------
 E-mail <sa...@ib...>  WWW: <http://www.ibrium.se>
  Phone/fax: (home) +46 8 4418431, (work) +46 8 7908470   
----------------------------------------------------------

New AFFS

[Michel <mic...@ii...>]

Roman Zippel wrote:

> Log message:
>   correctly initialize s_last_bmap
> 
> Modified files:
>       2.3/fs/affs/:
>         Changes bitmap.c
> 
>   Revision      Changes    Path
>   1.4           +6 -0      2.3/fs/affs/Changes
>   1.5           +4 -2      2.3/fs/affs/bitmap.c

Do you consider it stable enough for new binaries?


-- 
Earthling Michel Dänzer (MrCooper)    \   Debian GNU/Linux (powerpc) developer
CS student, Free Software enthusiast   \        XFree86 and DRI project member

CVS Update: 2.3 (branch: trunk)

[Roman Z. <zi...@us...>]

CVSROOT:	/cvsroot/linux-apus
Module name:	2.3
Repository:	2.3/fs/affs/
Changes by:	zippel@usw-pr-cvs1.	01/04/18 13:18:28

Log message:
  correctly initialize s_last_bmap

Modified files:
      2.3/fs/affs/:
        Changes bitmap.c 
  
  Revision      Changes    Path
  1.4           +6 -0      2.3/fs/affs/Changes
  1.5           +4 -2      2.3/fs/affs/bitmap.c

Re: MOL

[Glenn H. <gh...@c2...>]

Hello 

On 16-Apr-2001, Alan wrote:

> hi,

>> I have now tested this new version of MOL using a 2.4.3 kernel.
>> First it complained about unresolved symbol 'find_path_device',
>> so I added a find_path_device function that just returned NULL in
>> apus_setup.c (after looking at the mol-branch sources).

> :-) 
> 
>> NIP: FFF00544 XER: 20000000 LR: 10002B94 SP: 7FFFFC80 REGS: c5dd9e90
>> TRAP: 0200

> Geert mentioned that itslooking for a ROM in memory...did you tell MOL to
> use a New World ROM Image , or just ran MOL ?

I have configured it to use a new world rom. (in /etc/molrc)
I don't have a rom image, so I don't know if it will work with one present,
but I was expecting it to complain about a missing rom file when it couldn't
find it...


- glenn

Re: MOL

[Alan B. <al...@ms...>]

hi,

> I have now tested this new version of MOL using a 2.4.3 kernel.
> First it complained about unresolved symbol 'find_path_device',
> so I added a find_path_device function that just returned NULL in
> apus_setup.c (after looking at the mol-branch sources).

:-) 
 
> NIP: FFF00544 XER: 20000000 LR: 10002B94 SP: 7FFFFC80 REGS: c5dd9e90 TRAP: 0200

Geert mentioned that itslooking for a ROM in memory...did you tell MOL to
use a New World ROM Image , or just ran MOL ?

alan