linux-apus-devel

Re: the FTP site and the other stuff

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

hi,

> The stuff on the Project Page is located on download.sourceforge.net. Stuff
> can be uploaded there via incoming.

ah...found them.

> If you have time Alan, please upload everything from the FTP area there (old
> versions for the modules can be uploaded, just give the correct date) and move
> it to obsolete.

hmmm, this doesnt give much scope - i like all the file areas that are in 
the FTP directories... it also allows people to just mirror the stuff to
their harddrive. with the current situation you have to CVS to get the 
kernel source and then use web browser (or FTP) to get the boothack and
kernel image. 

what would people think if I cleaned up the FTP area (and also moved some
older modules to the linux-apus modules area) and got the latest 2.2.x and
2.3.x via CVS and placed those into FTP (so less experienced people can
just keep using FTP to get latest LinuxAPUS source code kernel?)

just an idea......

alan

Re: the FTP site and the other stuff

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

Alan Buxey wrote:

> can anyone tell me the relationship between the linux-apus FTP site
> and the work that can be downloaded from the linux-apus Web site?
> 
> I ask because the FTP area on sourceforge
> 
> linux-apus.sourceforge.net/pub/linux-apus
> 
> holds only old boothacks, and I'm not happy about the age of the v2.2.x
> and v2.3.x directories either.

There's no relationship.

The stuff on the Project Page is located on download.sourceforge.net. Stuff
can be uploaded there via incoming.

If you have time Alan, please upload everything from the FTP area there (old
versions for the modules can be uploaded, just give the correct date) and move
it to obsolete.


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

the FTP site and the other stuff

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

hi,

can anyone tell me the relationship between the linux-apus FTP site
and the work that can be downloaded from the linux-apus Web site?

I ask because the FTP area on sourceforge

linux-apus.sourceforge.net/pub/linux-apus

holds only old boothacks, and I'm not happy about the age of the v2.2.x
and v2.3.x directories either.

any enlightenment please?

alan

Re: New boothack

[Sven O. <Sve...@st...>]

Hello Nicholai

on 30-Jun-00 wrote Nicholai Benalal:

> Hi,

> I've released a new bootstrap. It's available from the project homepage.
> The following has changed:

> * Roman's patch. Stuff he needed for 2.3.xx
> * sys: inhibited last of all filesystems
> * assembly instruction that caused a crash on Giorgio's hw is removed

The new Version works on my A4000 with WarpOS ;-)

Thanks


Regards
-- 

Sve...@St...
ac-...@fr...

no RISC, no FUN

New boothack

[Nicholai B. <nic...@ch...>]

Hi,

I've released a new bootstrap. It's available from the project homepage. The
following has changed:

* Roman's patch. Stuff he needed for 2.3.xx
* sys: inhibited last of all filesystems
* assembly instruction that caused a crash on Giorgio's hw is removed


/Nicholai Benalal

Re: 2.4 report

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

Frank Petzold wrote:

> What really made me happy was that I could finally burn a CD with my
> IDE CD-R (2.2 freezes when cdrecord is invoked). So, SCSI-generic and
> IDE-SCSI both work.

Very cool. Can you please add a comment to that bug?


> Unfortunately, I was not able to make either amiserial nor MFCIII serial
> work. amiserial did not compile (neither as module nor in kernel) and it
> looks like the MFC stuff was never compiled at all.

MFC might not be in 2.4, but Jouko or Roman should have a working amiserial.


> BTW, amifb shows unresolved symbols when compiled as a module.

Hey, you're a developer, aren't you? ;)


Michel


-- 
Why drink & drive when you can smoke and fly???
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86, Team *AMIGA*, AUGS

2.4 report

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

I have done some tests with the 2.3 (2.4-test2) kernel yesterday. It
boots, and I can compile a kernel under it. 

What really made me happy was that I could finally burn a CD with my
IDE CD-R (2.2 freezes when cdrecord is invoked). So, SCSI-generic and
IDE-SCSI both work.

Unfortunately, I was not able to make either amiserial nor MFCIII serial
work. amiserial did not compile (neither as module nor in kernel) and it
looks like the MFC stuff was never compiled at all.

BTW, amifb shows unresolved symbols when compiled as a module.
-- 
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: Optimized ppcboot.c

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

Giorgio Terzi wrote:

> I attach only the source code of ppcboot.c because last
> time i sent a mail, the mailing-list administrator complained
> because it was more than 40kb of lenght.

That complaint was automatically generated by the Mailman software. We could
easily remove the limit, but is it really needed? There's a patch manager for
submitting code.


Michel


-- 
UNIX is like Sex:
If you don't know it, you don't miss it. But if you know it, you'll need it.
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86, Team *AMIGA*, AUGS

[Fwd: struct Node offsets Problem fixed (i think)]

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

Giorgio, you sent the post to the -admin address (bascially to Sven and me :)


Michel


-------- Original Message --------
Subject: struct Node offsets Problem fixed (i think)
Date: Tue, 27 Jun 2000 19:49:12 +0200
From: Giorgio Terzi <de...@ip...>
To: lin...@li...,Nicholai Benalal
<nic...@ch...>

Hello all,

(because of alignments ;-)  please read this e-mail with something
like a plain editor, with fixed width font, thanks).

As you know i have found an alignment problem in offset calculation
of the Node structure when interfacing with existing AmigaDos code.
Simply gcc assumes to even align the structure members,  so bytes
grow to be shorts and structure effective offsets CHANGE!!!
If we create something of new there is not problem, but if we try to 
read something in system created structures (struct Node for example)
we will find crashes or at better exceptions.
I think that the solution is this:

struct Node                                 offsets
{                                      packed   not packed
   struct Node  *ln_Succ;                 0          0
   struct Node  *ln_Pred;                 4          4
   UBYTE         ln_Type;                 8          8
   BYTE          ln_Pri;                  9          a
   char         *ln_Name;                 a          c
} __attribute__ ((aligned (2), packed));

i have added in the tail of the struct Node declaration the
__attribute__ keyword with the aligning parameters you see
in the above example in the Node.h header file.
As the docs say this "packs" the structure and word align it.  
It works!
But if someone has other ideas or solutions is welcome because i do 
not think to know gcc options so well to be mathematically sure
that this is the only way to solve the problem. 

Kind regards
-- 
             Giorgio Terzi

Re: Optimized ppcboot.c

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

Hi,

> * assembly instruction that caused a crash on Giorgio's hw is removed (still seems
> to work fine on other hw)

Sorry, I forgot to answer earlier. Anyway, that instruction did 
initialized a register that only exists on PPC64 cpu's, so the
effect is simply undefined on our hardware.

bye, Roman

Re: Optimized ppcboot.c

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

Hello, 

On 28-Jun-2000, Nicholai wrote:

> Would be nice if a few more ppl tested this before we release a new
> package. The bins are on the cvs (they are so small anyway). 

I just tested this, and it works fine here.
ppcboot_wup works with my CyberStormPPC board now.
Great work :-)


--
Glenn

Re: Optimized ppcboot.c

[Nicholai B. <nic...@ch...>]

Hello Giorgio

Den 27-Jun-00, skrev Giorgio Terzi:

GT> Hello Nicholai,
GT> i think i have done the work you have request to me.
GT> I am sorry...
GT> That function was more than messy but i worked
GT> only on the idea not in the code.
GT> Now the coding work is done. And now it is , at least,
GT> more readable...i hope.
GT> I attach only the source code of ppcboot.c because last
GT> time i sent a mail, the mailing-list administrator complained 
GT> because it was more than 40kb of lenght.
GT> 
GT> 

Good work Giorgio! I like this :-)
Your changes are now commited to the cvs. It's probably time for a new
release soon. The following has changed since the last one:

* Roman's patch. Stuff he needed for 2.3.xx
* sys: inhibited last of all filesystems
* assembly instruction that caused a crash on Giorgio's hw is removed (still seems
to work fine on other hw)

Would be nice if a few more ppl tested this before we release a new package. The
bins are on the cvs (they are so small anyway). I think it would be enough
to distribute bins, and readmes. The source can stay on the cvs in the
future.

Btw Giorgio, you should send your mails to
lin...@li.... Forget about the admin list!

Friendly,

Nicholai  

struct Node offsets Problem fixed (i think) (fwd)

[Nicholai B. <nic...@ch...>]

*** Vidaresänt brev, ursprungligen skrivet av Giorgio Terzi den 27-Jun-00 ***

Hello all,

(because of alignments ;-)  please read this e-mail with something
like a plain editor, with fixed width font, thanks).

As you know i have found an alignment problem in offset calculation
of the Node structure when interfacing with existing AmigaDos code.
Simply gcc assumes to even align the structure members,  so bytes
grow to be shorts and structure effective offsets CHANGE!!!
If we create something of new there is not problem, but if we try to 
read something in system created structures (struct Node for example)
we will find crashes or at better exceptions.
I think that the solution is this:

struct Node                                 offsets
{                                      packed   not packed
   struct Node  *ln_Succ;                 0          0
   struct Node  *ln_Pred;                 4          4
   UBYTE         ln_Type;                 8          8
   BYTE          ln_Pri;                  9          a
   char         *ln_Name;                 a          c
} __attribute__ ((aligned (2), packed));

i have added in the tail of the struct Node declaration the
__attribute__ keyword with the aligning parameters you see
in the above example in the Node.h header file.
As the docs say this "packs" the structure and word align it.  
It works!
But if someone has other ideas or solutions is welcome because i do 
not think to know gcc options so well to be mathematically sure
that this is the only way to solve the problem. 

Kind regards
-- 
             Giorgio Terzi

*** End of forwarded message ***

impport 2.4.0-test2 done

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

Hi,

> > I'm currently importing the latest bitkeeper tree, but I still have the
> > branch problem (support request is pending), so please don't commit
> > anything yet (if you need to update something else use "-r
> > apus_20000626").
> 
> Okay.

Now everyone can enjoy a new 2.4.0-test2 kernel. :)
I hope I didn't messed anything up. I included a version of amiserial that
compiles and seems to work at least as a module. I tested it at 9600 with
no flow control and I had no problems (but I didnt try very hard), Jouko, 
can you give it a try?

> BTW can you also (at least theoretically ;) merge our code back into BK?

No, I have no write access there.

bye, Roman

Re: How do I get Z cards recognized by APUS?

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

On Mon, 26 Jun 2000, Ken Tyler wrote:
> On Mon, 26 Jun 2000, F. Heitkamp wrote:
> > I want to get my Hypercomm4+ and Delfina Plus
> > cards recognized by APUS.  How/where does the
> > information reside?  I thought there was a
> > file that had a data base of all the cards?
> > Is that in boothack?
> 
> /include/linux/zorro.h contains all (most ?) of the zorro IDs

The full list is in zorroutils.

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: PowerUP SCSI driver.

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

"F. Heitkamp" wrote:

> > 1. Fred please join as a developer and share your code! :)
> 
> Are there any folks out there that want to help work on
> this driver?  Last I checked either no one had the same
> hardware as I, or did not, have the time, or simply wasn't
> interested.

Does that really matter? If nothing else, you get a CVS repository for free.
And I'd be surprised if noone would step out to test and/or work on the code
once it is there.


> There could be a problem with alignment of the cache, but I'm
> not sure how to check that out.  I guess I am going to peer
> at some of the other SCSI drivers and see what they do.

Endianness is correct?


Michel


-- 
The three Rs of Microsoft support: Retry, Reboot, Reinstall.
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86, Team *AMIGA*, AUGS

Re: PowerUP SCSI driver.

[Ken T. <ke...@we...>]

On Mon, 26 Jun 2000, F. Heitkamp wrote:

> Are there any folks out there that want to help work on
> this driver?  Last I checked either no one had the same
> hardware as I, or did not, have the time, or simply wasn't
> interested.

I've got the same hardware but no SCSI disks on the PPC SCSI interface so
probably can't help much. 

> The cache seems to be got by using check_region/request_region,
> which are standard kernel API calls AFAICT. The check_region
> call succeeds, and according to the "Linux Device Drivers"
> book the request_region will never fail if the check_region
> succeeds.

The driver you're looking might be similar to the 53c7xx driver, it gets
memory for the script (and for command buffers) by calling
get_free_page(), the CPU needs the virtual address of this memory but the
SCSI chip needs the physical address (see previous mail Fred).  Don't know
anything about reigons but do you need to set the cache mode of the memory
you get, the 53c7xx driver sets it to IOMAP_NOCACHE_SER.

The relevant part of 53c7xx.c is 

    instance->hostdata[0] = __get_free_pages(GFP_ATOMIC, 1);   
    if (instance->hostdata[0] == 0)
        panic ("53c7xx: Couldn't get hostdata memory");
    memset((void *)instance->hostdata[0], 0, 8192);
    cache_push(virt_to_phys((void *)(instance->hostdata[0])), 8192);
    cache_clear(virt_to_phys((void *)(instance->hostdata[0])), 8192);
    kernel_set_cachemode(instance->hostdata[0], 8192, IOMAP_NOCACHE_SER);

and later on to get the cache test (Test 1) running

        start = virt_to_bus (hostdata->script) + hostdata->E_test_1;
        hostdata->state = STATE_RUNNING;
        printk ("scsi%d : test 1", host->host_no);
        NCR53c7x0_write32 (DSP_REG, start);

I should get back to the 53c7xx driver...

Ken.

Re: How do I get Z cards recognized by APUS?

[Ken T. <ke...@we...>]

On Mon, 26 Jun 2000, F. Heitkamp wrote:

> I want to get my Hypercomm4+ and Delfina Plus
> cards recognized by APUS.  How/where does the
> information reside?  I thought there was a
> file that had a data base of all the cards?
> Is that in boothack?

/include/linux/zorro.h contains all (most ?) of the zorro IDs

Ken.

Re: PowerUP SCSI driver.

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

On Mon, Jun 26, 2000 at 06:43:51AM -0400, F. Heitkamp wrote:
> Are there any folks out there that want to help work on
> this driver?  Last I checked either no one had the same
> hardware as I, or did not, have the time, or simply wasn't
> interested.

I will surely test it.
-- 
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: PowerUP SCSI driver.

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

> The first dmesg output is one in which the return statements
> in the ncr_snooptest() are commented out in order to allow
> what looks like debugging code at the end of the routine
> to execute.  Assuming that is what's happening shows that
> the scripts are not executing.  The second dmesg output is
> showing what happens with the return statements back in
> their proper place.

Silly idea, but is there a difference in behaviour when you boot 
with 'nobats' or not?

If the '770 uses the same sort of scripting as the '710 then it may need
this to get the cache settings on the pages properly done.

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

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

How do I get Z cards recognized by APUS?

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

I want to get my Hypercomm4+ and Delfina Plus
cards recognized by APUS.  How/where does the
information reside?  I thought there was a
file that had a data base of all the cards?
Is that in boothack?

-- 
Fred

Re: PowerUP SCSI driver.

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

On Mon, Jun 26, 2000 at 09:53:20AM +0200, Michel D?nzer wrote:
> "F. Heitkamp" wrote:
> > 
> > I'm still at a loss to figure out why the cache test
> > is failing on the 53c770.c driver.  I have been comparing
> > the code in 53C770.c with that in the SYM53X8XX.c driver
> > and the ncr_snooptest() routines are pretty much the same.
> 
> Two things:
> 
> 1. Fred please join as a developer and share your code! :)

Are there any folks out there that want to help work on
this driver?  Last I checked either no one had the same
hardware as I, or did not, have the time, or simply wasn't
interested.

> 
> 2. Is there still no support for the 53c770 in the 2.3 kernel? There are even
> two 53c7xx drivers now...

Hmmm.  I'll have a look.  I think the 770 chip may have been
used in some UNIXes or RAID controllers, but since it doesn't
have a PCI bus interface, it was probably not used in PCs.

> 
> 
> > From looking at the code it seems like the ncr_snooptest()
> > is copying the SCSI scripts code to the cache and then
> > trying to execute that code.  Since that execution fails
> > the cache test fails.
> > [...]
> > ncr_snooptest(): CACHE TEST FAILED: timeout.
> > CACHE INCORRECTLY CONFIGURED.
>   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Have you checked the cache configuration options? ;)
> 
> What cache is this about?

I am, by no means, an expert on these drivers but I 
think the cache is a place in memory for the SCSI chip
to store and execute its scripts.  It may also be a
common area for the host processor and the SCSI chip
to share data.  Any insight would be appreciated.

The cache seems to be got by using check_region/request_region,
which are standard kernel API calls AFAICT. The check_region
call succeeds, and according to the "Linux Device Drivers"
book the request_region will never fail if the check_region
succeeds.

There could be a problem with alignment of the cache, but I'm
not sure how to check that out.  I guess I am going to peer
at some of the other SCSI drivers and see what they do.


-- 
Fred

Re: import 2.3 in progress

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

Roman Zippel wrote:

> I'm currently importing the latest bitkeeper tree, but I still have the
> branch problem (support request is pending), so please don't commit
> anything yet (if you need to update something else use "-r
> apus_20000626").

Okay.


> Anyway, as it's actually 2.4.0-test2, we could start discussing how the
> 2.4 source should be managed.
> I usually use rev$SUBLEVEL$EXTRAVERSION, but if we use the bitkeeper tree
> that doesn't really work, as they often also include pre-patches, so that
> I'm currently use bk_<date> and apus_<date> for working tags.

Sounds good to me.

BTW can you also (at least theoretically ;) merge our code back into BK?


Michel


-- 
I'm so hungry, I could almost eat health food.
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86, Team *AMIGA*, AUGS

import 2.3 in progress

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

Hi,

I'm currently importing the latest bitkeeper tree, but I still have the
branch problem (support request is pending), so please don't commit
anything yet (if you need to update something else use "-r
apus_20000626").
Anyway, as it's actually 2.4.0-test2, we could start discussing how the
2.4 source should be managed.
I usually use rev$SUBLEVEL$EXTRAVERSION, but if we use the bitkeeper tree
that doesn't really work, as they often also include pre-patches, so that
I'm currently use bk_<date> and apus_<date> for working tags.

bye, Roman

Re: Modified version of ppcboot.c

[nicholai <mp...@ch...>]

>> Hehe...we changed to another list and we are now using a cvs for >> the kernel sources as well as for boothack. Please take a look at
>> linux-apus.sourceforge.net for more information. And join the devlist! :-)

>Yep. Nicholai, have you committed the changes?
>

Not yet but I will once we've discussed the changes.

/Nicholai