linux-apus-devel

Re: 2.4.0-test4 problem

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

On Mon, Jul 24, 2000 at 01:07:54PM +0200, Michel Dänzer wrote:
> 
> 
> Using either the 990106 or latest boothack, doesn't boot, just resets the
> machine when it should switch to the pm2fb display. Nothing from {boot,d}mesg.
> 
> What on earth could cause such strange behaviour?

2.4.0-test4 boots for me. At least it did yesterday.
-- 
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.

2.4.0-test4 problem

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

Using either the 990106 or latest boothack, doesn't boot, just resets the
machine when it should switch to the pm2fb display. Nothing from {boot,d}mesg.

What on earth could cause such strange behaviour?


Michel


-- 
                               Reboot America.
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86, Team *AMIGA*, AUGS

Re: File not found in CVS

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

Giorgio Terzi wrote:

> > I don't understand what you're referring to here?
> >
> > Michel
> >
> 
> You're right because i was ignoring everything about CVS. I do not knew
> that command,  but now that  i've read the docs  i apologize for my
> ignorance and that stupid questions!

Hey, no problem. Everyone has had to learn those things at first :)


> I have committed my changes in CVS  repository  i hope without mistakes. :-)

Cool, I've just built an up-to-date kernel without problems. Unfortunately, I
can't test the new drivers for lack of hardware - Alan, when will a new test
kernel be ready? Or I could put one up tomorrow if you don't have time...


Michel


-- 
Man invented language to satisfy his deep need to complain.
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86, Team *AMIGA*, AUGS

Re: File not found in CVS

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

Giorgio Terzi wrote:

> > It seems that CVSweb has some problems currently - have you checked out a
> > working copy of the repository?
> 
> No. I was downloading from CVS the last versions of the files that needed to
> be patched by me and i have not found that file.
> I can restore it with my patches if it is not changed from the 2.2.10
> kernel's 2000-05-02 diff file. May i ?

Hmm - if that file is missing, I suspect something is severely broken in the
CVS repository. I have the file in my working copy of the repository, and I
don't think someone intentionally nor accidentally removed it (CVSweb doesn't
even show an Attic in that directory). Anyone has an idea what might be going
on?


> Do you mean a sort of test of the CVS archive integrity ?

I don't understand what you're referring to here?


Michel


-- 
Sometimes you have to stride boldly up to life,
 look it straight in the eye, and say "huh?"
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86, Team *AMIGA*, AUGS

Re: File not found in CVS

[Giorgio T. <de...@ip...>]

Hello Michel,  


> It seems that CVSweb has some problems currently - have you checked out a
> working copy of the repository?

No. I was downloading from CVS the last versions of the files that needed to be
patched by me and i have not found that file.
I can restore it with my patches if it is not changed from the 2.2.10 kernel's 
2000-05-02 diff file. May i ?

Do you mean a sort of test of the CVS archive integrity ?   
 
Regards
-- 
                                                 Giorgio Terzi

Re: File not found in CVS

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

Giorgio Terzi schrieb:

> i can't find the file config.in in the directory arch/ppc in
> linux 2.2 CVS repository.This is needed to add the menuconfig
> calls for drivers choice.

It seems that CVSweb has some problems currently - have you checked out a
working copy of the repository?


Michel


-- 
Software is like sex; it's better when it's free
 -- Linus Torvalds
______________________________________________________________________________
Michel Dänzer                             ///           mda...@ea...
                                     __  /// 	     AmigaOS/Linux(Debian/PPC)
Student of computer science at the   \\\///   Team *AMIGA*      ICQ #: 5675698
Swiss Federal Institute of Technology \\\/   AUGS member #163      IRC: CoOpER

Re: bugs 64500 and 64823

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

On Sat, Jul 15, 2000 at 07:52:09AM +1000, Anthony Towns wrote:
> Hello world,
> 
> After installing b-f 2.2.16, 64500 and 64823 still seem to be
> open. Are these RC? Are they already fixed? Do they require a 2.2.17 be
> built? What's the deal?

Hello, ...

I posted a message about it some week ago, but i don't see it anywehere, so i
suppose it got lost.

The 64500 bug is still there, i don't know how to fix it, and got not very
much (usefull) response to my call for help mail, on this list, nor really
from the linux-apus mailing list, so i guess most people there are not so
interrested in it, ...

It has been confirmed by another apus user (Michel Dänzer), and Erik Andersen
promised to have a look into the busybox mount, but i didn't hear again from
him.

The problem is that, using the exactly same kernel, when i do the following :

  # mount -r -t vfat -o loop=/dev/loop0 rescue.bin /mnt

when booting from the root image, i get a :

  Mounting rescue.bin on /mnt failed : block device required

which naturally hinders the install os kernel & modules menu option.

but when ignoring this option and the configure modules, installing the rest
of the stuff as usual, and then booting (again with the exact same kernel)
into the newly installed root partition, the above mentioned command works
without problem.

Michel Daenzer has reported that when doing :

  # mount -r -t vfat -o loop rescue.bin /mnt

from the root image it works ok, and rescue.bin get mounted into the loop0
device.

naturally i checked that the /dev/loop0 device is available and readable (it
has the same rights in both root /dev).

Ok, this is the current status. Now, what can we do about it ?

It is possible to install debian/ppc/apus in the current state of things, but
a newbie would need further help about this, and i best would provide that
help before the release, if we cannot fix the problem.

I preconize the following possible solution :

  * We decide not to support ppc/apus officially, :(((

  * We ship in the current status, but in this case, i would remove the
    "install os kernel & modules" as well as the "configure modules" menu
    options. The documentation would need to be updated to show the propper 
    install procedure. Ideally, we could just install and configure by hand
    the kernel-image-2.2.10-apus kernel package after the install.

  * We install the modules from the provided apus/drivers.tgz tarball, thus no
    need for mounting the rescue disk (as anyway, the kernel is not needed on
    the linux partition, since we have no lilo-like boot option). I tried to
    do this, but didn't want to mess with the dbootstrap stuff who did this,
    that i didn't understand. dbootstrap code can be particularly obscure at
    times :(((.

In any way, please keep me informed about this issue, so i can update the docs
accordingly before the release.

Hope this is helpful information ...

Friendly,

Sven LUTHER

File not found in CVS

[Giorgio T. <de...@ip...>]

Hello,

i can't find the file config.in in the directory arch/ppc in 
linux 2.2 CVS repository.This is needed to add the menuconfig 
calls for drivers choice.
or something is changed? 

Kind regards
-- 
                                                 Giorgio Terzi

Re: 2.4.0-test4 update

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

Hi,

I've just commited a few changes to fix sysrq finally and I added the
amiga scsi drivers options to drivers/scsi/Config.in, if someone doesn't
like to see the other drivers, feel free to fix it. :)

bye, Roman

Re: APUS bus access

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

On Tue, 18 Jul 2000, Arno Griffioen wrote:
> > BTW  Gerard said the driver should be MMIO and not IO_MAPPED. I may try
> > turning off I/O mapped and see what happens.  He also said he would have
> > liked to work on MMIO, on non-PC hardware I presume, but has no hardware
> > to do the work.  Does anyone have any ideas on MMIO vs IO MAPPED?  On
> > first thought I'm not sure I understand the differences.
> 
> Probably some subtle difference. MMIO should be the way we're used to on the
> 680x0 and PPC. 'flat' register space in memory. No special tricks required,
> just a base-address and some offsets.
> 
> I'm not sure what the difference would be between MMIO and IO_MAPPED, but 
> perhaps it's some way of mapping the Intel I/O port concept onto 
> memory. That my require some tricks when accessing (eg. write register 
> number first, then read or write data).
> 
> Perhaps Geert has seen this difference before in video-cards? They also
> have all sorts of MMIO and I/O mapping stuff.

Intel CPUs have separate memory and I/O spaces, while a 680x0 has memory space
only.

I/O space is meant for I/O devices (obviously) and uses special I/O
instructions ({in,out}[bwl]) to access I/O registers.

Memory space I/O (MMIO) means you just read/write from/to memory to access the
I/O registers that are located at the specified memory address.

I/O space allows you to have the full memory space populated with RAM, and
still room for I/O devices in I/O space. But since you need more bus signals
(to differentiate between memory and I/O accesses) and more instructions
(normal memory access + special I/O instructions), modern CPUs don't have I/O
space anymore. If they need it, they just reserve some piece of memory for it,
and use the ordinary memory instructions to access it, while the host bridge
takes care of converting them to I/O accesses on the I/O bus (usually PCI
these days, with ISA behind a PCI/ISA bridge).

Under Linux/m68k, inb() and friends don't do anything on Amiga, since Amiga
doesn't have I/O space (except with your GG2, Arno :-).

Under Linux/PPC, inb() and friends just access MMIO at isa_io_base+offset
(cfr. <asm/io.h>). Indeed, on PReP and CHRP ISA and PCI I/O space is not real
I/O space, but MMIO at some specific address. On APUS, there's no I/O space
(AFAIK), so you always have to use MMIO.

Since you used I/O space (through inb() and friends), data written ended up
somewhere at the wrong address (uninitialized isa_io_base on APUS), which was
probably a 16-bit only address of whatever. Reading it back thus gave the
wrong value. Instead of inb() and friends you should read/write from/to memory
space directly, using in_be32() and friends. These do eieio as well, to
protect against reorderings.

BTW, I see some things in <asm/io.h> that shouldn't be there:

#if defined(CONFIG_APUS)
#define inw(port)               in_be16((u16 *)((port)+_IO_BASE))
#define outw(val, port)         out_be16((u16 *)((port)+_IO_BASE), (val))
#define inl(port)               in_be32((u32 *)((port)+_IO_BASE))
#define outl(val, port)         out_be32((u32 *)((port)+_IO_BASE), (val))
#else

Since APUS doesn't have I/O space, these should not be defined at all.

[ Hmm, they are defined to in_be16() and friends. Why??? ]

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

PowerPC Linux BOF and Conference Call Friday July 21 (fwd)

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

I guess APUS deserves this as well. Or are you all on the linuxppc-dev list?

---------- Forwarded message ----------
Date: Tue, 18 Jul 2000 10:32:36 -0400
From: rod...@us...
To: lin...@li..., yel...@li...
Cc: rod...@us..., aj...@ac...
Subject: PowerPC Linux BOF and Conference Call Friday July 21


To:  arch/ppc developers

I will be running the PowerPC Linux Birds Of a Feather meeting at the Linux
Symposium in Ottawa on Friday July 21 from 4:30-6:00PM (East Coast USA).
The meeting will be immediately after Paul Mackerras talk on ppp and Andrew
Tridgell's talk on rsync.    If you are going to the symposium, please look
for details there.   If you would like to join via teleconference and do
not already have the teleconference numbers, please send me your name and
your topic of interest and I will send you the passcode.    Please do not
forward or post the passcode or the teleconference will get jammed.
Also, do not request the passcode if you are going to be in Ottawa;  we
don't want you joining from another pub :-)

For more information on the symposium please visit.

http://www.linuxsymposium.org/2000

Thank you.

Greg Rodgers (rod...@us...)


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

Re: Missing symbols in 2.4.0-test3

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

Hi,

> Do you give the files (sticky) labels at commit time? It is easier then to
> check out an older version (like 2.4.0-test2 ;-))

Before I import a new version I tag the current version with e.g.
apus-2_4_0-test3. If you want to compare different versions, look for
the tag with cvs log <file> and then use it with cvs diff.

bye, Roman

2.4.0-test4 update

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

Hi,

I've just finished the update to 2.4.0-test4, beside of that no other
changes. Frank, I look into your patch in the evening, I don't think we
need the atari/mac/... options. :)

bye, Roman

Re: Missing symbols in 2.4.0-test3

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

On Wed, Jul 19, 2000 at 10:00:25AM +0200, Roman Zippel wrote:
> Hi,
> 
> > I have tried to get 2.4.0-test3 running, but several modules (slip, ppp, ...)
> > get an unresolved symbol error, namely "irq_stat".
> 
> irq_stat is exported in arch/ppc/kernel/ppc_ksyms.c, so it should be
> visible...

I have seen that. That's why I am asking here...

> System.map is a list of all Symbols, but that isn't used by the modutils,
> check /proc/ksyms instead.

OK.

> I'll update soon to 2.4.0-test4, so you can try that and I'll try the
> modules in the evening at home.

Do you give the files (sticky) labels at commit time? It is easier then to
check out an older version (like 2.4.0-test2 ;-))
-- 
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: Missing symbols in 2.4.0-test3

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

Hi,

> I have tried to get 2.4.0-test3 running, but several modules (slip, ppp, ...)
> get an unresolved symbol error, namely "irq_stat".

irq_stat is exported in arch/ppc/kernel/ppc_ksyms.c, so it should be
visible...

> This is strange, because
> this symbol is listed in the System.map (what do the letters there mean, 
> anyway?).

System.map is a list of all Symbols, but that isn't used by the modutils,
check /proc/ksyms instead.

> All this was fine in 2.4.0-test2.

I'll update soon to 2.4.0-test4, so you can try that and I'll try the
modules in the evening at home.

bye, Roman

Missing symbols in 2.4.0-test3

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

I have tried to get 2.4.0-test3 running, but several modules (slip, ppp, ...)
get an unresolved symbol error, namely "irq_stat". This is strange, because
this symbol is listed in the System.map (what do the letters there mean, 
anyway?).

All this was fine in 2.4.0-test2.
-- 
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.

Posted in Patch manager IOBlix zorro serial driver

[Giorgio T. <de...@ip...>]

Hello,

Posted to patch manager my 1.0a (beta) version of serial driver as
linux 2.2.10 diff file.

WARNING: THE DRIVER I HAVE ATTACHED TO MY 07-04-2000 
E-MAIL (1.0) DOES NOT WORK!
USE THIS !

History:
had some problems with ppp connection: my IOBlix driver was buggy!
Problem discovered:
Seems that the interface do not like 64 bytes of FIFO space as 16c654 has.
Changed to 32 bytes and all worked well!
Rewritten some functions: now the driver is very similar to Gordon Huby's 
Hipercom code because: 
a) same chip's family. 
b) seems more compact code.

Tested with: 
Null modem cable connected to amiga serial and one of the IOBlix ports 
at 115200 bps with Minicom and a 25Kbytes file transferred with zmodem 
Connected succesfully with my provider with ppp 2.3.7. to post the patch

To do:
Discover why with 64 bytes of FIFO it works bad.
After this try to write code to use the advanced features of 16C654:
AutoRTS-AutoCTS, DMA block transmission if possible, Xon-Xoff soft
protocol and dynamic FIFO trigger code.

Kind regards
-- 
                                                 Giorgio Terzi

Re: APUS bus access

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

> BTW  Gerard said the driver should be MMIO and not IO_MAPPED. I may try
> turning off I/O mapped and see what happens.  He also said he would have
> liked to work on MMIO, on non-PC hardware I presume, but has no hardware
> to do the work.  Does anyone have any ideas on MMIO vs IO MAPPED?  On
> first thought I'm not sure I understand the differences.

Probably some subtle difference. MMIO should be the way we're used to on the
680x0 and PPC. 'flat' register space in memory. No special tricks required,
just a base-address and some offsets.

I'm not sure what the difference would be between MMIO and IO_MAPPED, but 
perhaps it's some way of mapping the Intel I/O port concept onto 
memory. That my require some tricks when accessing (eg. write register 
number first, then read or write data).

Perhaps Geert has seen this difference before in video-cards? They also
have all sorts of MMIO and I/O mapping stuff.

								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')

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

Re: APUS bus access

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

On Tue, Jul 18, 2000 at 07:57:36AM -0400, fh...@at... wrote:
> In <200...@su...>, on 07/18/00 
>    at 01:21 PM, gri...@ps... (Arno Griffioen) said:
> 
> >Is there another register which you can abuse in some way? Is there
> >perhaps a status/control register which will enable you to test some
> >read/write actions by flipping some bits? 
> 
> Yes.  There may be some.  I was browsing the programmers manual last
> night.  There are some various debugging registers.
> 
> BTW  Gerard said the driver should be MMIO and not IO_MAPPED. I may try
> turning off I/O mapped and see what happens.  He also said he would have
> liked to work on MMIO, on non-PC hardware I presume, but has no hardware
> to do the work.  Does anyone have any ideas on MMIO vs IO MAPPED?  On
> first thought I'm not sure I understand the differences.

Is not mmio when you see the registers as one big memory chunk, like we are
used to on amiga, and io_mapped, when you see the register as a pair address +
data to be passed to the device like they used to do on pc hardware ?

Friendly,

Sven LUTHER

Re: APUS bus access

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

In <200...@su...>, on 07/18/00 
   at 01:21 PM, gri...@ps... (Arno Griffioen) said:

>Is there another register which you can abuse in some way? Is there
>perhaps a status/control register which will enable you to test some
>read/write actions by flipping some bits? 

Yes.  There may be some.  I was browsing the programmers manual last
night.  There are some various debugging registers.

BTW  Gerard said the driver should be MMIO and not IO_MAPPED. I may try
turning off I/O mapped and see what happens.  He also said he would have
liked to work on MMIO, on non-PC hardware I presume, but has no hardware
to do the work.  Does anyone have any ideas on MMIO vs IO MAPPED?  On
first thought I'm not sure I understand the differences.

Fred

Re: APUS bus access

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

> Hmm.. Any hints in the docs? (BTW. Where could I get those? A PDF file
> somewhere?)

Forget it.. Found 'em..

Printing now :-)

								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')

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

Re: APUS bus access

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

> >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..)
> 
> The register is listed in the docs as R/W.   Whether that means it does
> not mangle; I don't know.

Hmm.. Any hints in the docs? (BTW. Where could I get those? A PDF file
somewhere?)

> Maybe I should try writing the register in two 16 bit chunks.  The only
> problem I see with that is that I think the SCSI chip starts execution of
> the script upon filling of that register with the address.

Is there another register which you can abuse in some way? Is there perhaps
a status/control register which will enable you to test some read/write
actions by flipping some bits? 

								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')

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

Re: APUS bus access

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

In <200...@su...>, on 07/17/00 
   at 07:42 AM, gri...@ps... (Arno Griffioen) said:

>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..)

The register is listed in the docs as R/W.   Whether that means it does
not mangle; I don't know.

Maybe I should try writing the register in two 16 bit chunks.  The only
problem I see with that is that I think the SCSI chip starts execution of
the script upon filling of that register with the address.

Fred

Re: APUS bus access

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

On Mon, 17 Jul 2000, Arno Griffioen wrote:
> > > 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. 

Anyone who disassembled the AmigaOS driver?

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: New Mirror for APUS

[Jesper S. <js...@re...>]

>>>>> "Steffen" == Steffen Leistner <st....@gm...> writes:

Steffen> Hi Jesper, I have setting up a new Mirror:

Steffen> 	ftp://ftp.ironbyte.de/pub/ironbyte/apus

Steffen> or http://www.ironbyte.de/mirror/apus

Steffen> I have added a mirror cronjob any sunday 0030 CDT.  My Server
Steffen> is a private Machine (Dual-PIII/600, RedHat 6.1), connected
Steffen> with 100MBit to the ECRC-Backbone in Munich/Germany.
 
Steffen, the sunsite stuff has been obsoleted. Some of the other
developers may be able to help you set up a mirror of the sourceforge
stuff instead.

Jesper