linux-apus-devel

Re: APUS bus access

[<gri...@ps...>]

> Is there any reason the APUS kernel would not allow 32 bit access to the
> Amiga Hardware or memory especially on the PowerUP board?

No.

The only thing I can imagine is that the 604e always tries to do 64-bit read 
and write access to the hardware instead of 32bit. Don't know if it
can be forced to 32 bit..

The rest of the interfaceing to the Amiga is 'converted' by hardware. So
access to ZORRO-II devices 'automagically' results in 16 bit return values.
The rest of the hardware in the A3/4000 is pretty much fully 32 bit 
(except the custom-chips of course)

> > The reason I ask, is that when the driver puts the  "pc" value into the
> > DSP register it is bf2fe50, but when the value  is read back out it is
> > "bf2".
> 
> Weird ... 16 bit reversed in a DWORD + 16 bit lost.
> Or the BUS access reads 16 bits instead of 32 bits.

Can't imagine that to be true. The CV-PPC (also on the turboboard 
bus directly) works just fine except for some strange 640e related
problem in the XAA code in the X server.

Timing? Have you tried adding a delay-loop before reading the data again?
The chip may not like being hit again too quickly. 

We know Phase5 liked to cut a few corners here and there in the design,
so they may not have made it self-regulating. You may need to poll
some sort of 'status' bit to see if the chip is ready to accept
new read/write requests. 

> > To my logic it seems that either the  correct value may not have
> > got into the register due to an alignment problem, or the read back value
> > cannot be guaranteed to be
> > correct due to properties of the particular register.
> 
> If you write 32 bits at a given IO (MMIO) address and read back the same
> location and width, you should get all the 4 bytes, possibly in a
> different order if the glue that does IO is not endian-consistent.

Or if the device you write to immediately processes the input and in
the process mangles the external view of the register. 

It is a read/write register I hope.. (just checking..)

								Bye, Arno.

-- 
PSINetworks Europe           Fax: +31-23-5699841 | One disk to rule them all,
Siriusdreef 34               Tel: +31-23-5699840 | One disk to bind them,
2132WT Hoofddorp+--------------------------------+ One disk to hold the files
The Netherlands |   *  Musical Interlude  *      | And in the darkness grind 'em
----------------+--------------------------------+------------------------------

 We say Retribution, We say Vengeance is bliss, We say Revolution,
 With a Cast-Iron fist!                  (Megadeth, 'The Disintegrators')

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

APUS bus access

[<fh...@at...>]

Hi,

I posted a message on the Linux SCSI mailing list about the problems I am
having with the 53c770 driver.   The current maitainor
Gerard Rondier replied.

Is there any reason the APUS kernel would not allow 32 bit access to the
Amiga Hardware or memory especially on the PowerUP board?
  

> The reason I ask, is that when the driver puts the  "pc" value into the
> DSP register it is bf2fe50, but when the value  is read back out it is
> "bf2".

Weird ... 16 bit reversed in a DWORD + 16 bit lost.
Or the BUS access reads 16 bits instead of 32 bits.

> To my logic it seems that either the  correct value may not have
> got into the register due to an alignment problem, or the read back value
> cannot be guaranteed to be
> correct due to properties of the particular register.

If you write 32 bits at a given IO (MMIO) address and read back the same
location and width, you should get all the 4 bytes, possibly in a
different order if the glue that does IO is not endian-consistent.


Fred

Re: char devices and debugging

[Gordon H. <go...@gh...>]

fh...@at... wrote:
> 
> I have been trying to learn how to program char devices.
> Well really trying to get my Hypercom4+ and Delfina Plus cards
>  to work.  I've made test drivers for both.  Both drivers contain printk
> statements so I can see if they are doing anything remotely like they are
> supposed to.  Even though the drivers seem to  compile OK and are
> "installed" in the kernel, no printk statements are visible in the dmesg
> output.  Is this a problem peculiar to char devices?  I suspect I have not
> quite got the driver code installed correctly in the kernel source tree.

Try changing the printk's to
printk(KERN_INFO "Blah"); /* KERN_* are defined in linux/kernel.h */

then it may goto dmesg and the kernel log.

> Can anyone tell me the general procedure for adding a driver
> to the kernel?  i.e. so it can be chosen in the .config and loaded into
> the kernel?  Or maybe point me to some docs somewhere.

Sure, for 2.2 add a config option in arch/ppc/config.in and change
drivers/char/Makefile.

Or compile it as a module.

with gcc -c module.c -DMODULE -D__KERNEL__ -o module.o
then load the mod with /sbin/insmod module.o

Module programing infos at http://www.linuxdoc.org/LDP/lkmpg/mpg.html

Gordon

char devices and debugging

[<fh...@at...>]

I have been trying to learn how to program char devices.
Well really trying to get my Hypercom4+ and Delfina Plus cards
 to work.  I've made test drivers for both.  Both drivers contain printk
statements so I can see if they are doing anything remotely like they are
supposed to.  Even though the drivers seem to  compile OK and are
"installed" in the kernel, no printk statements are visible in the dmesg
output.  Is this a problem peculiar to char devices?  I suspect I have not
quite got the driver code installed correctly in the kernel source tree.

Can anyone tell me the general procedure for adding a driver
to the kernel?  i.e. so it can be chosen in the .config and loaded into
the kernel?  Or maybe point me to some docs somewhere.

Fred

53c770 SCSI

[<fh...@at...>]

Still trying to make some progress on the PowerUP SCSI
controller.  I noticed that when I try to read back the value from the dsp
register that it is not the same as the value
that was put into it which is the "pc" value   Does anyone 
think that is strange? Assuming the SCSI chip did not change  the value
for some reason, one would think it should be the  same as what was put
in.

Fred


Total memory = 64MB; using 256kB for hash table (at c0200000) Linux
version 2.2.10 (root@amiga1) (gcc version 2.95.2 19991024 (release)) #94
Sat Jul 15 20:51:52 EDT 2000 Amiga hardware found: [A4000T] VIDEO BLITTER
AUDIO FLOPPY A4000_SCSI A4000_IDE KEYBOARD MOUSE SERIAL PARALLEL A3000_CLK
CHIP_RAM PAULA LISA ALICE_NTSC ZORRO3  APUS: BATs=0, BUS=66MHz, RAM=70ns,
PCI bridge=1
time_init: decrementer frequency = 990000000/60
Console: colour dummy device 80x25
Calibrating delay loop... 395.67 BogoMIPS
Memory: 62156k available (1220k kernel code, 1536k data, 112k init)
[c0000000,c4000000] POSIX conformance testing by UNIFIX
Zorro: Probing AutoConfig expansion devices: 5 devices
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Unix domain sockets 1.0 for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
Starting kswapd v 1.5 
CV3D detected running in Z3 mode
Console: switching to colour frame buffer device 160x64
fb0: Cybervision/3D frame buffer device, using 4096K of video memory fb1:
Amiga AGA frame buffer device, using 1280K of video memory ****
apus_kbd_init_hw
M68K Serial driver version 1.01
ttyS0 at 0x80dff018: Amiga builtin
pty: 256 Unix98 ptys configured
lp_init: lp using interrupt driver
lp0: Builtin parallel port at 0x80bfe101
Amiga mouse installed.
DMA sound driver installed, using 4 buffers of 32k.
RAM disk driver initialized:  16 RAM disks of 4096K size
loop: registered device at major 7
ide0: Gayle IDE interface (A4000 style)
hda: ST34342A, ATA DISK drive
ide0 at 80dd2020 on irq 0x0000000c
hda: ST34342A, 4103MB w/128kB Cache, CHS=8894/15/63
FD: probing units
found <5>fd: drive 0 didn't identify, setting default ffffffff fd0 fd1 
scsi-ncr53c7xx : NCR53c710 at memory 0x80dd0040, io 0x0, irq 12 scsi0:
Revision 0x1
scsi0 : NCR code relocated to 0xbf365e8 (virt 0xc3f365e8)
scsi0 : test 1 started
Trying to detect PuP SCSI...
ncr53c8xx: 53c770 detected 
ncr53c770-0: rev=0x00, base=0xf40000, io_port=0x0, irq=12
new NCB[2924] @c3f35000.
Storing input
new SCRIPT[3772] @c3f34000.
new SCRIPTH[3708] @c3f2f000.
np: ID: 770 REV: 0 FEA: 15382 CLCK: 5 OF: 10
Initialize timer
paddr: f40000 paddr2: 0
io_port: 0
Peparing...
stuff: 0 0 0 0 1
set verbose:
myaddr: 0
myaddr: 0
myaddr: 7
ncr53c770-0: ID 7, Fast-20, Parity Checking
verbose:5
ncr53c770-0: initial SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex)
00/00/00/00/00/00 ncr53c770-0: final   SCNTL3/DMODE/DCNTL/CTEST3/4/5 =
(hex) 05/82/20/00/08/24 no on-board ram
NCR_IOMAPPED
BIG_ENDIAN
scripth: c3f2f000 p_scripth: bf2f000 script: c3f34000 p_script: bf34000
Resetting for snoop test
offset: c
istat: 0
SCSI reset
istat: 40
istat: 0
virt_to_phys(np): bf35000
np: c3f35000
ncr_cache: 0 pc: bf2fe50
nc_dsp: bf2
ncr_snooptest(): CACHE TEST FAILED: timeout.
CACHE INCORRECTLY CONFIGURED.
ncr53c770-0: detaching...
scsi0 : Amiga NCR53c710 SCSI
scsi : 1 host.
scsi0 : target 2 accepting period 200ns offset 8 5.00MHz synchronous SCSI
scsi0 : setting target 2 to period 200ns offset 8 5.00MHz synchronous SCSI
  Vendor: TOSHIBA   Model: CD-ROM XM-6201TA  Rev: 1037
  Type:   CD-ROM                             ANSI SCSI revision: 02
Detected scsi CD-ROM sr0 at scsi0, channel 0, id 2, lun 0 scsi0 : target 5
accepting period 204ns offset 8 4.90MHz synchronous SCSI scsi0 : setting
target 5 to period 208ns offset 8 4.80MHz synchronous SCSI
  Vendor: WANGTEK   Model: 51000  SCSI REV7  Rev: 3J  
  Type:   Sequential-Access                  ANSI SCSI revision: 01
Detected scsi tape st0 at scsi0, channel 0, id 5, lun 0 scsi : detected 1
SCSI tape 1 SCSI cdrom total.
Uniform CDROM driver Revision: 2.55
PPP: version 2.3.7 (demand dialling)
TCP compression code copyright 1989 Regents of the University of
California PPP line discipline registered.
eth0: Ariadne at 0x00ea0000, Ethernet Address 00:60:30:00:10:01 Partition
check:
 hda: RDSK hda1 hda2 hda3 hda4 hda5
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 112k init 32k prep 4k pmac 8k open firmware
Adding Swap: 73840k swap-space (priority -1)


-- 
-----------------------------------------------------------
fh...@at...
-----------------------------------------------------------

Re: MultifaceIII driver in 2.3

[Gordon H. <go...@gh...>]

Frank Petzold wrote:
> 
> I have tried to get the ser_mfc driver to run in 2.3. I have taken the
> driver from the 2.3.99pre2 tree of the m68k branch. Unfortunately, it
> tries to register itself witn m68k_register_serial, which does not seem
> to exist in 2.4.x, at least not in the APUS tree. I saw that amiserial.c
> contains prototypes of (un)register_serial, but these procedures are
> defined nowhere in the kernel (at least not in any .c file).

You've got the mfc3 driver, which also requires m68kserial.c from the
same branch. But AFAIK they are dropping m68kserial.c And the mf3 driver
as well.

So the mf3 driver will have to rewritten for 2.3. And It will have to be
a totally independent from m68kserial.c

> How is serial registring done in 2.4? I am completely clueless.

It will have to rewritten for 2.3. So register tty_driver. :)
Or just modify serial.c, which is easier.

--
BTW sorry for sending you this twice I forgot to CC the List
Gordon

DMAsound -Atari/Amiga/APUs/q40 (fwd)

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

Here's a backport of the dmasound splitting to 2.2.x.

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

---------- Forwarded message ----------
Date: Fri, 14 Jul 2000 13:04:39 +0100
From: Iain Sandoe <ia...@sa...>
To: lin...@li...
Subject: DMAsound -Atari/Amiga/APUs/q40


Update on version 2.

I can't see any differences between the split & un-split code for the
non-pmac platforms.

( there's one thing you'll have to do if you want to compile built-in)

http://www.drfruitcake.com/linux/linuxppc.html

So give it a whirl...

Iain.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: Enabling Amiga SCSI low level and MFCIII drivers

[Michel <da...@re...>]

Frank Petzold wrote:
> 
> I have just uploaded a patch to enable the Amiga SCSI low level drivers
> and the MFCIII driver in the 2.3 config and Makefiles.
> 
> The code for arch/ppc/config.in was taken from the 2.3.99pre2 m68k tree.

Hmm, I think it would be better if we added those drivers to
drivers/scsi/config.in, probably encapsulated by CONFIG_AMIGA.

Anyway, it's cool that I could also start really using 2.4 if the Blizzard
SCSI works.


Michel


-- 
The problem with religious texts is that the answers aren't in the back.
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86, Team *AMIGA*, AUGS

Re: 2.4.0-test3

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

Hi,

> but the bitkeeper server seems to be down...

Argh, they changed the server name, but I don't remember an
announcement...

bye, Roman

2.4.0-test3

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

Hi,

> All this was tested with the 2.4.0-test2. I saw a major update in the CVS
> yesterday, I will try with the new kernel and report back.

I've just committed the last changes to get 2.4.0-test3 working. I had to
use a few patches from test4-prex to get it compiled, so I expect a test4
soon, but the bitkeeper server seems to be down...

bye, Roman

Running 2.3

[<fp...@zu...>]

I now have managed (for the first time ever) to get all my Amiga HW to run
decently. This includes: CV64/3D, Modem (now on amiserial, MFCIII does not 
work), Scanner and ZIP on GVP Series II, CD writer on IDE bus.

This was made possible due to the 2.3 kernel not hanging when I access the CD
writer. This was the last problem. 

Of course, now there are still some minor ones:

- When I mount an AFFS partition with rw,noexec the system hangs (still beats).
- Under heavy IDE access load while online, I get "hda lost interrupt" hangs.
- Multiface III driver does not compile

All this was tested with the 2.4.0-test2. I saw a major update in the CVS
yesterday, I will try with the new kernel and report back.

It looks as I am permanently moving over to 2.4 now.
-- 
Frank Petzold, IBM Zurich Research Laboratory, Säumerstrasse 4,
CH-8803 Rüschlikon/Switzerland, Tel.  +41-1-724-84-42  Fax.   +41-1-724-89-56
 Business email: fp...@zu...          Private email: pe...@he...
   The opinions expressed here are mine and not necessarily those of IBM.

Enabling Amiga SCSI low level and MFCIII drivers

[<fp...@zu...>]

I have just uploaded a patch to enable the Amiga SCSI low level drivers
and the MFCIII driver in the 2.3 config and Makefiles.

The code for arch/ppc/config.in was taken from the 2.3.99pre2 m68k tree.

MFCIII ser_mfc.o does not compile, while the gvp11 driver works fine.
-- 
Frank Petzold, IBM Zurich Research Laboratory, Säumerstrasse 4,
CH-8803 Rüschlikon/Switzerland, Tel.  +41-1-724-84-42  Fax.   +41-1-724-89-56
 Business email: fp...@zu...          Private email: pe...@he...
   The opinions expressed here are mine and not necessarily those of IBM.

MultifaceIII driver in 2.3

[<fp...@zu...>]

I have tried to get the ser_mfc driver to run in 2.3. I have taken the
driver from the 2.3.99pre2 tree of the m68k branch. Unfortunately, it
tries to register itself witn m68k_register_serial, which does not seem 
to exist in 2.4.x, at least not in the APUS tree. I saw that amiserial.c 
contains prototypes of (un)register_serial, but these procedures are
defined nowhere in the kernel (at least not in any .c file).

How is serial registring done in 2.4? I am completely clueless.
-- 
Frank Petzold, IBM Zurich Research Laboratory, Säumerstrasse 4,
CH-8803 Rüschlikon/Switzerland, Tel.  +41-1-724-84-42  Fax.   +41-1-724-89-56
 Business email: fp...@zu...          Private email: pe...@he...
   The opinions expressed here are mine and not necessarily those of IBM.

Re: CALL FOR HELP : debian boot floppies 2.2.15 on apus still not ok.

[Sven L. <lu...@dp...>]

On Mon, Jul 10, 2000 at 10:40:10AM +0200, Michel Dänzer wrote:
> Sven LUTHER wrote:
> > 
> > On Sun, Jul 09, 2000 at 01:36:41PM -0700, Daniel Jacobowitz wrote:
> > > On Sun, Jul 09, 2000 at 10:24:36PM +0200, Michel Dänzer wrote:
> > > > > $ mount -r -t vfat -o loop=/dev/loop0 resceu.bin /mnt
> > > > >
> > > > > And see if it can be mounted ...
> > > >
> > > > It works if I omit the '=/dev/loop0' , and now on the second try (after
> > > > getting back to the installer main menu) df shows /dev/loop0 .
> > > >
> > > > So the problem must be elsewhere, any ideas?
> > >
> > > Oho!  Now that is interesting.  Is /dev/loop0 created properly (I think
> > > someone doublechecked that earlier...)?  If so, then I would blame the
> > > APUS kernel patches.
> > 
> > Ok, but remember, when i install the base tarball by hand, the above works
> > without problem, with the exact same kernel. But then modules are installed,
> > that is the only difference, but the loop module is builtin.
> > 
> > Could there be another module that has soime influence on this ?
> 
> You can find out very easily: lsmod will tell after you have mounted the
> image.
> 
> 
> What really caught my eye in the log though was that dbootstrap doesn't even
> use the -o loop[=...] mount option, it apparently uses losetup to initialize
> the loop device and then mounts from it directly. I feel the problem might be
> there somewhere.

Yes, it does some funny piping and other stuff, should look in the dbootstrap
code to get the exact command.

Friendly,

Sven LUTHER

Re: CALL FOR HELP : debian boot floppies 2.2.15 on apus still not ok.

[Michel <da...@re...>]

Sven LUTHER wrote:
> 
> On Sun, Jul 09, 2000 at 01:36:41PM -0700, Daniel Jacobowitz wrote:
> > On Sun, Jul 09, 2000 at 10:24:36PM +0200, Michel Dänzer wrote:
> > > > $ mount -r -t vfat -o loop=/dev/loop0 resceu.bin /mnt
> > > >
> > > > And see if it can be mounted ...
> > >
> > > It works if I omit the '=/dev/loop0' , and now on the second try (after
> > > getting back to the installer main menu) df shows /dev/loop0 .
> > >
> > > So the problem must be elsewhere, any ideas?
> >
> > Oho!  Now that is interesting.  Is /dev/loop0 created properly (I think
> > someone doublechecked that earlier...)?  If so, then I would blame the
> > APUS kernel patches.
> 
> Ok, but remember, when i install the base tarball by hand, the above works
> without problem, with the exact same kernel. But then modules are installed,
> that is the only difference, but the loop module is builtin.
> 
> Could there be another module that has soime influence on this ?

You can find out very easily: lsmod will tell after you have mounted the
image.


What really caught my eye in the log though was that dbootstrap doesn't even
use the -o loop[=...] mount option, it apparently uses losetup to initialize
the loop device and then mounts from it directly. I feel the problem might be
there somewhere.


Michel


-- 
...and that is how we know the Earth to be banana-shaped.
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86, Team *AMIGA*, AUGS

Re: CALL FOR HELP : debian boot floppies 2.2.15 on apus still not ok.

[Sven L. <lu...@dp...>]

On Sun, Jul 09, 2000 at 01:36:41PM -0700, Daniel Jacobowitz wrote:
> On Sun, Jul 09, 2000 at 10:24:36PM +0200, Michel Dänzer wrote:
> > > $ mount -r -t vfat -o loop=/dev/loop0 resceu.bin /mnt
> > > 
> > > And see if it can be mounted ...
> > 
> > It works if I omit the '=/dev/loop0' , and now on the second try (after
> > getting back to the installer main menu) df shows /dev/loop0 .
> > 
> > So the problem must be elsewhere, any ideas?
> 
> Oho!  Now that is interesting.  Is /dev/loop0 created properly (I think
> someone doublechecked that earlier...)?  If so, then I would blame the
> APUS kernel patches.

Huh ???

Ok, but remember, when i install the base tarball by hand, the above works
without problem, with the exact same kernel. But then modules are installed,
that is the only difference, but the loop module is builtin. 

Could there be another module that has soime influence on this ?

i append here a ls -lR of the modules of this kernel :

.:
total 16
drwxr-xr-x    2 root     root         4096 mai  2 19:26 block
drwxr-xr-x    2 root     root         4096 mai  2 19:26 fs
drwxr-xr-x    2 root     root         4096 mai  2 19:26 misc
drwxr-xr-x    2 root     root         4096 mai  2 19:26 net

./block:
total 36
-rw-r--r--    1 root     root        34568 mai  2 19:26 amiflop.o

./fs:
total 180
-rw-r--r--    1 root     root         7980 mai  2 19:26 binfmt_misc.o
-rw-r--r--    1 root     root        96819 mai  2 19:26 hfs.o
-rw-r--r--    1 root     root        41083 mai  2 19:26 minix.o
-rw-r--r--    1 root     root         5388 mai  2 19:26 nls_cp437.o
-rw-r--r--    1 root     root         4516 mai  2 19:26 nls_cp850.o
-rw-r--r--    1 root     root         3652 mai  2 19:26 nls_iso8859-1.o
-rw-r--r--    1 root     root         4236 mai  2 19:26 nls_iso8859-15.o

./misc:
total 48
-rw-r--r--    1 root     root         2884 mai  2 19:26 joy-amiga.o
-rw-r--r--    1 root     root        13568 mai  2 19:26 joystick.o
-rw-r--r--    1 root     root         4460 mai  2 19:26 lp_intern.o
-rw-r--r--    1 root     root         7328 mai  2 19:26 lp_m68k.o
-rw-r--r--    1 root     root         9736 mai  2 19:26 lp_mfc.o

./net:
total 160
-rw-r--r--    1 root     root         9164 mai  2 19:26 a2065.o
-rw-r--r--    1 root     root         9676 mai  2 19:26 ariadne.o
-rw-r--r--    1 root     root         6528 mai  2 19:26 bsd_comp.o
-rw-r--r--    1 root     root         6940 mai  2 19:26 hydra.o
-rw-r--r--    1 root     root        41096 mai  2 19:26 ppp.o
-rw-r--r--    1 root     root        46828 mai  2 19:26 ppp_deflate.o
-rw-r--r--    1 root     root         7396 mai  2 19:26 slhc.o
-rw-r--r--    1 root     root        16860 mai  2 19:26 slip.o

I did not see anything that could cause a problem, or could it ?

Friendly,

Sven LUTHER

Re: CALL FOR HELP : debian boot floppies 2.2.15 on apus still not ok.

[Sven L. <lu...@dp...>]

On Sun, Jul 09, 2000 at 10:24:36PM +0200, Michel Dänzer wrote:
> Sven LUTHER wrote:
> 
> > Everything works fine, but when i come to the step where i would normally do
> > :
> > 
> >   * install os kernel & modules
> > 
> > i give the corrct place in the requester, and dbootstrap tries to loop mount
> > the rescue.bin image to fetch the kernel and the modules, and fail.
> 
> Confirm that. ("Roger that" ;)
> 
> Messages from VT 3 I consider relevant:
> 
> running cmd 'mount -r -t ext2 /dev/loop0 /floppy'
> Mounting /dev/loop0 on /floppy failed: invalid argument
> 
> Looks like it tries to use /dev/loop0 as a fake floppy drive and fails.
> 
> 
> > I then tried testing by hand, with :
> > 
> > $ mount -r -t vfat -o loop=/dev/loop0 resceu.bin /mnt
> > Mounting rescue.bin on /mnt failed : block device required
> 
> It has just worked for me with just '-o loop', and I notice that it seems to
> be mounted from /dev/loop1 (df output).

Ok, nice to know that, will try this evening, ...

If that is true, it must most definitvely be related to the mount program, ...

> > $ mount -r -t vfat -o loop=/dev/loop0 resceu.bin /mnt
> > 
> > And see if it can be mounted ...
> 
> It works if I omit the '=/dev/loop0' , and now on the second try (after
> getting back to the installer main menu) df shows /dev/loop0 .

well, i confirm this works on my i386 box (changing resceu to rescue
naturally), as well as on apus, when i boot into the base install (with the
true mount)

Erik, what do you think about it ?

Friendly,

Sven LUTHER

Commit Notice

[Gordon H. <go...@gh...>]

Applied 2.2 patch by ghuby to fix unresolved symbols problem.

Regards

Gordon

Re: CALL FOR HELP : debian boot floppies 2.2.15 on apus still not ok.

[Daniel J. <da...@de...>]

On Sun, Jul 09, 2000 at 10:24:36PM +0200, Michel Dänzer wrote:
> > $ mount -r -t vfat -o loop=/dev/loop0 resceu.bin /mnt
> > 
> > And see if it can be mounted ...
> 
> It works if I omit the '=/dev/loop0' , and now on the second try (after
> getting back to the installer main menu) df shows /dev/loop0 .
> 
> So the problem must be elsewhere, any ideas?

Oho!  Now that is interesting.  Is /dev/loop0 created properly (I think
someone doublechecked that earlier...)?  If so, then I would blame the
APUS kernel patches.

Dan

/--------------------------------\  /--------------------------------\
|       Daniel Jacobowitz        |__|        SCS Class of 2002       |
|   Debian GNU/Linux Developer    __    Carnegie Mellon University   |
|         da...@de...         |  |       dm...@an...      |
\--------------------------------/  \--------------------------------/

Re: CALL FOR HELP : debian boot floppies 2.2.15 on apus still not ok.

[Michel <dae...@st...>]

Sven LUTHER wrote:

> Everything works fine, but when i come to the step where i would normally do
> :
> 
>   * install os kernel & modules
> 
> i give the corrct place in the requester, and dbootstrap tries to loop mount
> the rescue.bin image to fetch the kernel and the modules, and fail.

Confirm that. ("Roger that" ;)

Messages from VT 3 I consider relevant:

running cmd 'mount -r -t ext2 /dev/loop0 /floppy'
Mounting /dev/loop0 on /floppy failed: invalid argument

Looks like it tries to use /dev/loop0 as a fake floppy drive and fails.


> I then tried testing by hand, with :
> 
> $ mount -r -t vfat -o loop=/dev/loop0 resceu.bin /mnt
> Mounting rescue.bin on /mnt failed : block device required

It has just worked for me with just '-o loop', and I notice that it seems to
be mounted from /dev/loop1 (df output).


> $ mount -r -t vfat -o loop=/dev/loop0 resceu.bin /mnt
> 
> And see if it can be mounted ...

It works if I omit the '=/dev/loop0' , and now on the second try (after
getting back to the installer main menu) df shows /dev/loop0 .

So the problem must be elsewhere, any ideas?


Michel


-- 
Software is like sex; it's better when it's free  - Linus Torvalds
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86, Team *AMIGA*, AUGS

chipram.c update

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

While getting rid of occurrencies of my old email address, I sent following
patch to Linus (i.e. keep in sync with the corresponding m68k version).

--- native-2.4.0-test3-pre6/arch/ppc/amiga/chipram.c.orig	Sun Oct 10 11:10:32 1999
+++ native-2.4.0-test3-pre6/arch/ppc/amiga/chipram.c	Sat Jul  8 14:39:57 2000
@@ -1,15 +1,14 @@
 /*
 **  linux/amiga/chipram.c
 **
-**      Modified 03-May-94 by Geert Uytterhoeven
-**                           (Gee...@cs...)
+**      Modified 03-May-94 by Geert Uytterhoeven <ge...@li...>
 **          - 64-bit aligned allocations for full AGA compatibility
 */
 
-#include <linux/config.h>
 #include <linux/types.h>
 #include <linux/kernel.h>
 #include <linux/init.h>
+#include <linux/zorro.h>
 #include <asm/amigahw.h>
 
 struct chip_desc {
@@ -25,6 +24,8 @@
 u_long amiga_chip_size;
 static unsigned long chipavail;
 
+static struct resource chipram = { "Chip RAM", 0 };
+
 unsigned long amiga_chip_avail( void )
 {
 #ifdef DEBUG
@@ -34,8 +35,7 @@
 }
 
 
-__init
-void amiga_chip_init (void)
+void __init amiga_chip_init (void)
 {
   struct chip_desc *dp;
 
@@ -49,6 +49,8 @@
    */
   amiga_chip_size -= 0x4000;
 #endif
+  chipram.end = amiga_chip_size-1;
+  request_resource(&iomem_resource, &chipram);
 
   /* initialize start boundary */
 
@@ -72,7 +74,7 @@
 #endif
 }
 
-void *amiga_chip_alloc (long size)
+void *amiga_chip_alloc(long size, const char *name)
 {
 	/* last chunk */
 	struct chip_desc *dp;
@@ -82,7 +84,7 @@
 	size = (size + 7) & ~7;
 
 #ifdef DEBUG
-   printk("chip_alloc: allocate %ld bytes\n", size);
+   printk("amiga_chip_alloc: allocate %ld bytes\n", size);
 #endif
 
 	/*
@@ -108,14 +110,14 @@
 		dp = DP((unsigned long)ptr + dp->length);
 		dp->alloced = 1;
 #ifdef DEBUG
-		printk ("chip_alloc: no split\n");
+		printk ("amiga_chip_alloc: no split\n");
 #endif
 	} else {
 		/* split the extent; use the end part */
 		long newsize = dp->length - (2*sizeof(*dp) + size);
 
 #ifdef DEBUG
-		printk ("chip_alloc: splitting %d to %ld\n", dp->length,
+		printk ("amiga_chip_alloc: splitting %d to %ld\n", dp->length,
 			newsize);
 #endif
 		dp->length = newsize;
@@ -134,14 +136,18 @@
 	}
 
 #ifdef DEBUG
-	printk ("chip_alloc: returning %p\n", ptr);
+	printk ("amiga_chip_alloc: returning %p\n", ptr);
 #endif
 
 	if ((unsigned long)ptr & 7)
-		panic("chip_alloc: alignment violation\n");
+		panic("amiga_chip_alloc: alignment violation\n");
 
     chipavail -= size + (2*sizeof(*dp)); /*MILAN*/
 
+    if (!request_mem_region(ZTWO_PADDR(ptr), size, name))
+	printk(KERN_WARNING "amiga_chip_alloc: region of size %ld at 0x%08lx "
+	       "is busy\n", size, ZTWO_PADDR(ptr));
+
     return ptr;
 }
 
@@ -156,6 +162,7 @@
 #endif
 	/* deallocate the chunk */
 	sdp->alloced = edp->alloced = 0;
+	release_mem_region(ZTWO_PADDR(ptr), sdp->length);
 
 	/* check if we should merge with the previous chunk */
 	if (!sdp->first && !sdp[-1].alloced) {

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- Linux/{m68k~Amiga,PPC~CHRP} -- 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: 2.4.0-test2 kernel

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

Hello 

On 07-Jul-2000, Michel wrote:

>>>> (Unable to access
>>>> /dev/ttyS0 : No such device).

>> You either haven't compiled in serial port support or haven't loaded the
>> module (amiserial.o).

>> No, I have serial port support compiled in. I even tried to compile a new
>> kernel just to make sure. I selected support for Amiga serial port in the
>> config.

>> CONFIG_AMIGA_BUILTIN_SERIAL=y

>> Are there any other options I have to set to make it work ?

> Are there any boot messages about the serial (sup)port?

Nope. Guess it should be, right ?

If someone with working serialsupport could send me their config file so
that I can find out what I'm doing wrong, that
would be great.


- glenn

Re: 2.4 amiserial

[Jes S. <je...@li...>]

>>>>> "Geert" == Geert Uytterhoeven <ge...@li...> writes:

Geert> On 6 Jul 2000, Jes Sorensen wrote:
>>  Just irritates me that every user has to deselect a pile of
>> unsupported ISA/PCI drivers.

Geert> These should be inside CONFIG_{ISA,PCI}, or done using
Geert> `dep_{bool,tristate} * $CONFIG_{ISA,PCI}'. Anyone volunteering
Geert> to do the clean up?

True, once this has been done *and* accepted into Linus' tree, then
lets move ours.

Jes

Re: 2.4.0-test2 kernel

[Michel <dae...@st...>]

Glenn Hisdal wrote:

> >> I got 2.3.10-3 which was the latest I could find on ftp.linuxppc.org.
> >> pppd now recognizes the ppp support, but is not able to access
> >> /dev/ttySx, so I can't communicate with the modem. (Unable to access
> >> /dev/ttyS0 : No such device).
> 
> > You either haven't compiled in serial port support or haven't loaded the
> > module (amiserial.o).
> 
> No, I have serial port support compiled in. I even tried to compile a new
> kernel just to make sure. I selected support for Amiga serial port in the
> config.
> 
> CONFIG_AMIGA_BUILTIN_SERIAL=y
> 
> Are there any other options I have to set to make it work ?

Are there any boot messages about the serial (sup)port?


Michel


-- 
Me? A skeptic? Can you prove it?
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86, Team *AMIGA*, AUGS

Re: 2.4.0-test2 kernel

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

Hello, 

On 06-Jul-2000, Michel wrote:

>>> Get the latest pppd, IIRC 2.3.11 is needed for 2.4 .

>> I got 2.3.10-3 which was the latest I could find on ftp.linuxppc.org.
>> pppd now recognizes the ppp support, but is not able to access
>> /dev/ttySx, so I can't communicate with the modem. (Unable to access
>> /dev/ttyS0 : No such device).

> You either haven't compiled in serial port support or haven't loaded the
> module (amiserial.o).

No, I have serial port support compiled in. I even tried to compile a new
kernel just to make sure. I selected support for Amiga serial port in the
config.

CONFIG_AMIGA_BUILTIN_SERIAL=y     

Are there any other options I have to set to make it work ?


- glenn