Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

>> Oops. It was not my intention to offend anyone. Excuses if I did. > No offense taken, I assure you :-) ;-) > I need to diagnose this in more detail really. I'll have to consult Stephen > on > how to replace modules in the install initrd image so kernel fixes can be > tested without a full

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi, > > > case. Given that the lock handling of IDE may be dodgy, that scares > me a bit. > > > > Reasons enough for you? > > Oops. It was not my intention to offend anyone. Excuses if I did. No offense taken, I assure you :-) > > > I'll focus on getting SCSI fixed, first and foremost. First

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi, > > The reasons for this are: > > EtherNEC needs to be rewritten based on the current ne.c code. I'm not sure if > > ... > > processing before the ethernet device has been opened. > > I did recently rewrite the EtherNAT driver based on the current smc91x.c one. > > ... > > work out. > > > >

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi Geert, > > > When Michael thinks they're ready, he can submit them to netdev or > > > linux-scsi > > > ;-) > > > > I'm happy for them to live in linux-m68k :-) > > > > EtherNEC and EtherNAT are 'ready' in the sense they are working reliably. > > They > > are by no means 'ready in the sense

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Fri, 31 Oct 2008, Michael Schmitz wrote: > > > > Looking at the SCSI driver in 2.6.26, it's no surprise - the error > > > > handling > > > > update that I did for 2.6.18 is not included in Geert's current 2.6 > > > > patch > > > > series. Looks like I botched the patch submission way back wh

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi, > I'll focus on getting SCSI fixed, first and foremost. First stab at this is > attached (not fudging with the timeouts, but failing the request instead if > the > lock cannot be obtained). > > Stephen, can you try to apply that one to the current Debian installer > kernel? > If it fails

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi, > > > Looking at the SCSI driver in 2.6.26, it's no surprise - the error > > > handling > > > update that I did for 2.6.18 is not included in Geert's current 2.6 patch > > > series. Looks like I botched the patch submission way back when. > > > > It's a pity. You put so much work in it bu

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Thu, 30 Oct 2008, Frank P. Szymanski wrote: > > Looking at the SCSI driver in 2.6.26, it's no surprise - the error handling > > update that I did for 2.6.18 is not included in Geert's current 2.6 patch > > series. Looks like I botched the patch submission way back when. > > It's a pity. You

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

> Looking at the SCSI driver in 2.6.26, it's no surprise - the error handling > update that I did for 2.6.18 is not included in Geert's current 2.6 patch > series. Looks like I botched the patch submission way back when. It's a pity. You put so much work in it but none of your patches (EtherNEC

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi, > > Imagine my frustration when my 2.6.27 kernel started spewing IO errors while > > I can. :-( I guessed so. > > reading from the designated partition. Something's gone dodgy with SCSI > > again. > > Well. That's what I suppose as well. Looking at the SCSI driver in 2.6.26, it's no sur

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi Michael, > Well, I ran into trouble reading from CD the other day, and it all culminated > in > the CD being marked offline after repeated IO errors. That was with a 24x > SCSI > drive which I had bought for use on Atari and Mac ten years ago. The drive > hat > gotten a bit dodgy already

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi Frank, > > Can you checksum that file on another computer, to check if the CD is > > OK? If there is md5sum in the install ramdisk, you may be able to > > checksum it from the installer itself as well. > > Checked it. The checksum is fine. Well, I ran into trouble reading from CD the other da

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi Michael, On Sun, 19 Oct 2008, Michael Schmitz wrote: > > > > You can rsync from e.g. > > > > rsync://rsync.kernel.org/pub/linux/kernel/people/geert/linux-m68k-patches-2.6 > > > > > > Thanks, that worked like a charm (other than your include move patche > > > breaking > > > because elf.

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi Geert, You can rsync from e.g. rsync://rsync.kernel.org/pub/linux/kernel/people/geert/linux-m68k-patches-2.6 Thanks, that worked like a charm (other than your include move patche breaking because elf.h got changed). Updated. But I commented that patch out anyway. We know it would work (f

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Sat, 18 Oct 2008, Michael Schmitz wrote: > > > I'd like to have a more streamlined way of syncing Geert's patch queue - > > > can > > > git or rsync be used for that, Geert? > > > > You can rsync from e.g. > > rsync://rsync.kernel.org/pub/linux/kernel/people/geert/linux-m68k-patches-2.6 > > Th

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi Frank, Can you checksum that file on another computer, to check if the CD is OK? If there is md5sum in the install ramdisk, you may be able to checksum it from the installer itself as well. Checked it. The checksum is fine. I had another go with the dayli etch ISO as of Thursday, the kern

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi Geert, I'd like to have a more streamlined way of syncing Geert's patch queue - can git or rsync be used for that, Geert? You can rsync from e.g. rsync://rsync.kernel.org/pub/linux/kernel/people/geert/linux-m68k-patches-2.6 Thanks, that worked like a charm (other than your include move pa

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi Geert, Regarding performance afforded by having a 100 Mbit PHY instead of a 10 Mbit one: EtherNAT: 210 KB/s out, 140 KB/s in (scp of a 35 MB vmlinux file) EtherNEC: 175 KB/s out, 128 KB/s in (same file) Hardly worth it, eh? That's slower than my Ariadne? Still no interrupts. BTW, do y

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

> Can you checksum that file on another computer, to check if the CD is > OK? If there is md5sum in the install ramdisk, you may be able to > checksum it from the installer itself as well. Checked it. The checksum is fine. Regards, Frank -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a su

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Wed, Oct 15, 2008 at 06:54:12AM +0200, Michael Schmitz wrote: > Hi, > >>> Christian's apartment isn't suited for keeping a powerful build cluster, >>> from what I hear. >> >> Stephen has seen it, I have more computers than chairs... my build machine >> at home is either a Via C7 at 1.5GHz or my

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Wed, Oct 15, 2008 at 09:37:58AM +0200, Petr Stehlik wrote: > Michael Schmitz píše v St 15. 10. 2008 v 08:53 +0200: > > >> According to sparemint, getting their cross compiler package as well as > > >> the sparemint CVS should build the toolchain semi-automatically. I'll > > >> give that a try. >

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Michael Schmitz píše v St 15. 10. 2008 v 08:53 +0200: > >> According to sparemint, getting their cross compiler package as well as > >> the sparemint CVS should build the toolchain semi-automatically. I'll > >> give that a try. > > > > easy can be good. > > May just be a third sort of opaque, thou

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi, The powerpc toolchains would help me already. Pushing those to http://people.debian.org/~smarenka/tmp/ Thanks, pulled. Now what do I need from there - mintlib, gemlib? mintlib OK. According to sparemint, getting their cross compiler package as well as the sparemint CVS should bui

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi, Christian's apartment isn't suited for keeping a powerful build cluster, from what I hear. Stephen has seen it, I have more computers than chairs... my build machine at home is either a Via C7 at 1.5GHz or my old P4 notebook at 2GHz. First I want to replace the notebook with a netbook, but

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi Michael, On Thu, 4 Sep 2008, Michael Schmitz wrote: > as you've probably noticed, my previous EtherNAT patch does not compile > without this one being applied as well. > > Comments welcome (is there anyone on this list with access to an EtherNAT > card, > besides cts and myself?). > >

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Wed, Oct 15, 2008 at 02:20:45AM +1100, Finn Thain wrote: > On Tue, 14 Oct 2008, Stephen R Marenka wrote: > > On Tue, Oct 14, 2008 at 01:12:03PM +1100, Finn Thain wrote: > > It's already in the .27 queue. It seemed to apply fine to .26. :\ > > Probably the debian sources already have a backport

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Tue, 14 Oct 2008, Stephen R Marenka wrote: > On Tue, Oct 14, 2008 at 01:12:03PM +1100, Finn Thain wrote: > > mac-reinstate-rtc.diff > > fbcon-remove-broken-mac-vbl-handler.diff > > mac-esp-fix-for-quadras-with-two-esp-chips.diff > > mac-macfb-do-not-overflow-fix-id.diff > > > > IIRC the abo

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Tue, Oct 14, 2008 at 06:35:15AM +0200, Michael Schmitz wrote: > > > >Excuses, excuses ;) > > His last build machine must've overheated and died in summer :-) > Christian's apartment isn't suited for keeping a powerful build cluster, > from what I hear. Stephen has seen it, I have more co

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Tue, 14 Oct 2008, Stephen R Marenka wrote: > On Tue, Oct 14, 2008 at 10:15:07AM +0200, Geert Uytterhoeven wrote: > > On Tue, 14 Oct 2008, Michael Schmitz wrote: > > > > > Thats all I did, as long as I remembered not to include the patch that > > > > > should never be included... it breaks the wh

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Mon, Oct 13, 2008 at 10:21:32PM +0200, Michael Schmitz wrote: >>> Do you have notes left on how to build the toolchain? >> >> I found my amiga toolchain notes and what look like two atari toolchains >> for powerpc, but no notes. :\ > > The powerpc toolchains would help me already. Pushing those

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Tue, Oct 14, 2008 at 10:15:07AM +0200, Geert Uytterhoeven wrote: > On Tue, 14 Oct 2008, Michael Schmitz wrote: > > > > Thats all I did, as long as I remembered not to include the patch that > > > > should never be included... it breaks the whole build in really > > > > interesting > > > > > > Y

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Tue, Oct 14, 2008 at 01:12:03PM +1100, Finn Thain wrote: > > > On Mon, 13 Oct 2008, Geert Uytterhoeven wrote: > > > On Mon, 13 Oct 2008, Stephen R Marenka wrote: > > > On Tue, Oct 14, 2008 at 12:21:57AM +1100, Finn Thain wrote: > > > > I have some patches for your 2.6.25/26 kernels too (mainl

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Tue, Oct 14, 2008 at 09:27:45AM +0200, Geert Uytterhoeven wrote: > On Tue, 14 Oct 2008, Finn Thain wrote: > > On Mon, 13 Oct 2008, Geert Uytterhoeven wrote: > > > On Mon, 13 Oct 2008, Stephen R Marenka wrote: > > > > On Tue, Oct 14, 2008 at 12:21:57AM +1100, Finn Thain wrote: > > > > > I have so

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Tue, 14 Oct 2008, Michael Schmitz wrote: > > > Thats all I did, as long as I remembered not to include the patch that > > > should never be included... it breaks the whole build in really > > > interesting > > > > Yes, the patch that must not be. > > Is that the patch that must not be named as

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Tue, 14 Oct 2008, Christian T. Steigies wrote: > Thats all I did, as long as I remembered not to include the patch that > should never be included... it breaks the whole build in really interesting > ways otherwise. It would be great if Geert submitted his patches directly to > the debian-kernel

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Mon, 13 Oct 2008, Michael Schmitz wrote: > We'll have to follow Geert's patch queue for development kernels, meaning we > need to swap out obsolete patches or add new ones in the right order. I'll try > to help with that. > > I'd like to have a more streamlined way of syncing Geert's patch queu

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Tue, 14 Oct 2008, Finn Thain wrote: > On Mon, 13 Oct 2008, Geert Uytterhoeven wrote: > > On Mon, 13 Oct 2008, Stephen R Marenka wrote: > > > On Tue, Oct 14, 2008 at 12:21:57AM +1100, Finn Thain wrote: > > > > I have some patches for your 2.6.25/26 kernels too (mainly to fix a > > > > problem wi

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi, Sorry, I am quite happy you doing it ;-) Also, I currently don't have a fast machine with sufficient space for cross-compiling. Excuses, excuses ;) His last build machine must've overheated and died in summer :-) Christian's apartment isn't suited for keeping a powerful build cluste

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Mon, 13 Oct 2008, Geert Uytterhoeven wrote: > On Mon, 13 Oct 2008, Stephen R Marenka wrote: > > On Tue, Oct 14, 2008 at 12:21:57AM +1100, Finn Thain wrote: > > > I have some patches for your 2.6.25/26 kernels too (mainly to fix a > > > problem with dual scsi busses and a problem with xorg).

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Tue, Oct 14, 2008 at 12:16:16AM +0200, Christian T. Steigies wrote: > On Mon, Oct 13, 2008 at 04:09:47PM -0500, Stephen R Marenka wrote: > > >> > > >> Those patches are *not* in -8 for sid. I guess I'll have to make > > >> another run at the patch queue. (Unless cts wakes back up or someone > >

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Mon, Oct 13, 2008 at 11:45:13PM +0200, Michael Schmitz wrote: >> Getting your head around the build system is at least as much fun. > > It still is? I must admit, this is what made me flee any d-i work in the > first place (having built Mac installers on a Quadra ten years ago). The kernel bu

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Mon, Oct 13, 2008 at 04:09:47PM -0500, Stephen R Marenka wrote: > >> > >> Those patches are *not* in -8 for sid. I guess I'll have to make > >> another run at the patch queue. (Unless cts wakes back up or someone > >> else wants to be kernel patch dude. Hint, Hint. ;) Sorry, I am quite happy yo

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Those patches are *not* in -8 for sid. I guess I'll have to make another run at the patch queue. (Unless cts wakes back up or someone else wants to be kernel patch dude. Hint, Hint. ;) Counter-hint: I don't. I have strong misgivings about anything that involves CVS or SVN access to kernel or d-i

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Mon, Oct 13, 2008 at 10:11:38PM +0200, Michael Schmitz wrote: > Hi Stephen, > >>> atari-ethernec-fixes.diff (also add atari-ethernec-IRQF_SHARED.diff if >>> ethernec and ethernat are to be used in the same kernel). >> >> Those patches are *not* in -8 for sid. I guess I'll have to make >> another

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Mon, Oct 13, 2008 at 09:56:31PM +0200, Michael Schmitz wrote: > Hi Stephen, > Are they in Geert's queue yet? If so, as what? >>> >>> Sure. The aformentioned one is >>> mac-esp-fix-for-quadras-with-two-esp-chips.diff > > It does seem the etch-m68k kernel installer is missing another patch of

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Do you have notes left on how to build the toolchain? I found my amiga toolchain notes and what look like two atari toolchains for powerpc, but no notes. :\ The powerpc toolchains would help me already. I can put the toolchains up if they'd be of any help. I think most of the source came fro

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi Stephen, atari-ethernec-fixes.diff (also add atari-ethernec-IRQF_SHARED.diff if ethernec and ethernat are to be used in the same kernel). Those patches are *not* in -8 for sid. I guess I'll have to make another run at the patch queue. (Unless cts wakes back up or someone else wants to be ke

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi Stephen, Are they in Geert's queue yet? If so, as what? Sure. The aformentioned one is mac-esp-fix-for-quadras-with-two-esp-chips.diff It does seem the etch-m68k kernel installer is missing another patch of mine. I got the dreaded oops at ikbd_reset... The patch in question is the one

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Mon, Oct 13, 2008 at 09:07:54PM +0200, Geert Uytterhoeven wrote: > On Mon, 13 Oct 2008, Stephen R Marenka wrote: > > On Tue, Oct 14, 2008 at 12:21:57AM +1100, Finn Thain wrote: > > > I have some patches for your 2.6.25/26 kernels too (mainly to fix a > > > problem with dual scsi busses and a pr

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Mon, 13 Oct 2008, Stephen R Marenka wrote: > On Tue, Oct 14, 2008 at 12:21:57AM +1100, Finn Thain wrote: > > I have some patches for your 2.6.25/26 kernels too (mainly to fix a > > problem with dual scsi busses and a problem with xorg). > > Are they in Geert's queue yet? If so, as what? Sure.

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi, > Something seems to be wrong with your CD-ROM drive ... can you try > inserting the disk only after Linux has booted? Well, that's what I suppose it the problem for now. I downloaded the latest iso from stephen's site and regardless of what I do I now always get the following result: [!!]

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Tue, Oct 14, 2008 at 12:21:57AM +1100, Finn Thain wrote: > I have some patches for your 2.6.25/26 kernels too (mainly to fix a > problem with dual scsi busses and a problem with xorg). Are they in Geert's queue yet? If so, as what? > > We need to figure out the patches for experimental too.

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Mon, 13 Oct 2008, Stephen R Marenka wrote: > On Mon, Oct 13, 2008 at 03:44:05AM +0200, Michael Schmitz wrote: > > Hi Stephen, > > > >>> Hopefully. Did you also apply my patch that fixes the 'interrupt > >>> from stopped card' problem? That one does include fixes that default > >>> the IO ba

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Mon, Oct 13, 2008 at 03:55:59AM +0200, Michael Schmitz wrote: > Hi, > >>> I guess not. I have never built TOS binaries from Linux myself. Roman >>> Hodek or Andreas Schwab had built a cross compiler and a TOS libc package >>> but I'm not sure these are still working. >> >> I built the 5.6 ones i

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Mon, Oct 13, 2008 at 03:44:05AM +0200, Michael Schmitz wrote: > Hi Stephen, > >>> Hopefully. Did you also apply my patch that fixes the 'interrupt from >>> stopped card' problem? That one does include fixes that default the IO >>> base address to 0x300 so the io=0x300 module argument is no longe

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi, I guess not. I have never built TOS binaries from Linux myself. Roman Hodek or Andreas Schwab had built a cross compiler and a TOS libc package but I'm not sure these are still working. I built the 5.6 ones in the archive, but I'll have to recreate the toolchain again. It's on my long list

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi Stephen, Hopefully. Did you also apply my patch that fixes the 'interrupt from stopped card' problem? That one does include fixes that default the IO base address to 0x300 so the io=0x300 module argument is no longer required. Is it in Geert's queue? If so, which one? atari-ethernec-fixes

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Sun, Oct 12, 2008 at 10:12:40PM +0200, Michael Schmitz wrote: > I guess not. I have never built TOS binaries from Linux myself. Roman > Hodek or Andreas Schwab had built a cross compiler and a TOS libc package > but I'm not sure these are still working. I built the 5.6 ones in the archive, b

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Sun, Oct 12, 2008 at 09:38:12PM +0200, Michael Schmitz wrote: > Hi, > >>> That means it got past the point where the EtherNEC load failed >>> previously (right at kernel boot time, before the installer gets >>> started). >> >> Hopefully it's a module now? > > Hopefully. Did you also apply my pat

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi Frank, That means it got past the point where the EtherNEC load failed previously (right at kernel boot time, before the installer gets started). Yes. So the driver is indeed provided as a module now. Good. The file rename sure can be done in the nect ISO, fixing the cause of the hang m

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi, That means it got past the point where the EtherNEC load failed previously (right at kernel boot time, before the installer gets started). Hopefully it's a module now? Hopefully. Did you also apply my patch that fixes the 'interrupt from stopped card' problem? That one does include fixe

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi Michael, > That means it got past the point where the EtherNEC load failed > previously (right at kernel boot time, before the installer gets started). Yes. > The file rename sure can be done in the nect ISO, fixing the cause of > the hang may required changes to the bootstrap itself... Well

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Sat, Oct 11, 2008 at 03:38:13AM +0200, Michael Schmitz wrote: > Hi, > >> Yes, you are right. Tried it several times again with different >> networking cards (EtherNEC, EtherNAT and NetUsBee) but none of them >> worked. It stops at "loading optitude" (6%). > > That means it got past the point whe

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi, Yes, you are right. Tried it several times again with different networking cards (EtherNEC, EtherNAT and NetUsBee) but none of them worked. It stops at "loading optitude" (6%). That means it got past the point where the EtherNEC load failed previously (right at kernel boot time, before th

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi Michael, >> Just a little self-comment. Seems that I've been too impatient. Tried it >> again today and it worked until Linux wants to recognize an ethernet >> card. > :-) Well, it would need the network card fopr a net install I guess. So we are on-topic again. :-) Yes, you are right. Tried i

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi Frank, The installation procedure run beyond the point where you had to enter the country you live in, the keyboard layout, then it recognized my cd-roms correctly (2 scsi drives connected externally). Then the screen went blue and nothing else happened. Just a little self-comment. Seems

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

> The installation procedure run beyond the point where you had to enter > the country you live in, the keyboard layout, then it recognized my > cd-roms correctly (2 scsi drives connected externally). > Then the screen went blue and nothing else happened. Just a little self-comment. Seems that I'

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

>> O.K. Copied everything to harddisc. What happened then is that after I >> started bootstra.prg from partition c:\ (GEMDOS) with MiNT the computer >> just freezed. When I started from partition c:\ with TOS the computer >> reboots (coldboot). > NVDI included, or not? Without NVDI, just plain TOS

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi again, Output from Bootstra.prg: Linux/68k AtariBootstrap version 6.0snapshot Dec 13 2004 Copyright 1993-2004 by Arjan Knor, Robert de Vries, Roman Hodek, Andreas Schwab, Petr Stehlik Kernel command line: root=/dev/ram video=atafb:vga16 console=tty load_ramdisk=1 fb=false BOOT_IMAGE=c:\linu

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi, O.K. Copied everything to harddisc. What happened then is that after I started bootstra.prg from partition c:\ (GEMDOS) with MiNT the computer just freezed. When I started from partition c:\ with TOS the computer reboots (coldboot). NVDI included, or not? I just remembered something else

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

> I had that screen corruption one - tried it again and it worked. Only > difference: the initrd was located on the HD as well as the bootargs. O.K. Copied everything to harddisc. What happened then is that after I started bootstra.prg from partition c:\ (GEMDOS) with MiNT the computer just freeze

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi, O.K. Even though I still didn't receive my ct63 yet I gave it another try. Tried the etch netinstall iso from the source above mentioned. After I started bootstra.prg from harddisk in 16 colour vga mode on my ct60 falcon with the following bootargs the ide led started to flash, after a whil

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

>> Where are the current isos located? > Ahh, iso's (runs screaming into the night). > is the > canonical place for the daily cd buildds. > I'm in the process of getting those working again. > Hopefully I'll have something reasonable for

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Tue, Sep 16, 2008 at 10:47:41PM +0200, Frank P. Szymanski wrote: > >> The only disadvantage is that I still don't have a running debian/m68k > >> machine due to the fact that the installer refused to work on my machine. > > Where did it fail? :) > > Actually, I don't remember. It has been half

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

>> The only disadvantage is that I still don't have a running debian/m68k >> machine due to the fact that the installer refused to work on my machine. > Where did it fail? :) Actually, I don't remember. It has been half a year ago or more. At the moment I am waiting for my ct63 so I can use the fa

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Tue, Sep 16, 2008 at 08:39:20PM +0200, Frank P. Szymanski wrote: > The only disadvantage is that I still don't have a running debian/m68k > machine due to the fact that the installer refused to work on my machine. Where did it fail? :) Peace, Stephen -- Stephen R. Marenka If life's not

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi Michael, > And I was wondering all the time who the Atari expert was who didn't > make it to the meeting :-) ;-) >>> Is there a MiNT driver for the USB port on the EtherNAT as well? That >>> might be useful to tackle next. >> Unfortunately not. There is only a closed source beta mouse driver.

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Tue, 16 Sep 2008, Geert Uytterhoeven wrote: > On Tue, 16 Sep 2008, Michael Schmitz wrote: > > Anyway, in this case asking the EtherNAT developers for information > > regarding > > USB HCD base address and interrupts is perhaps the easiest way forward. > > Some googling reveals it uses the Phil

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Tue, 16 Sep 2008, Michael Schmitz wrote: > > > Is there a MiNT driver for the USB port on the EtherNAT as well? That > > > might be useful to tackle next. > > Unfortunately not. There is only a closed source beta mouse driver. > > > > http://www.janthomas.org.uk/ > > That won't help much ... >

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi Frank, Sure - I wasn't sure whether you still followed the list though. Well. I still read it on a regular basis but as I don't have much to contribute I do not post messages quite often. It's a pity I couldn't join the developer's meeting. :-( I was really looking forward to it. And I wa

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi Michael, >>> Comments welcome (is there anyone on this list with access to an >>> EtherNAT card, >>> besides cts and myself?). >> >> Here (but I guess you already knew that?). > > Sure - I wasn't sure whether you still followed the list though. Well. I still read it on a regular basis but as I

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Sat, 6 Sep 2008, Wouter Verhelst wrote: > On Thu, Sep 04, 2008 at 11:57:56PM +0200, Michael Schmitz wrote: > > Regarding performance afforded by having a 100 Mbit PHY instead of a 10 Mbit > > one: > > > > EtherNAT: 210 KB/s out, 140 KB/s in (scp of a 35 MB vmlinux file) > > EtherNEC: 175 KB/s ou

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

On Thu, Sep 04, 2008 at 11:57:56PM +0200, Michael Schmitz wrote: > Regarding performance afforded by having a 100 Mbit PHY instead of a 10 Mbit > one: > > EtherNAT: 210 KB/s out, 140 KB/s in (scp of a 35 MB vmlinux file) > EtherNEC: 175 KB/s out, 128 KB/s in (same file) > > Hardly worth it, eh? We

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi Frank, Comments welcome (is there anyone on this list with access to an EtherNAT card, besides cts and myself?). Here (but I guess you already knew that?). Sure - I wasn't sure whether you still followed the list though. Regarding performance afforded by having a 100 Mbit PHY instead of

Re: [patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi Michael, > Comments welcome (is there anyone on this list with access to an > EtherNAT card, > besides cts and myself?). Here (but I guess you already knew that?). > Regarding performance afforded by having a 100 Mbit PHY instead of a > 10 Mbit > one: > > EtherNAT: 210 KB/s out, 140 KB/s in (sc

[patch 3/2] m68k: Atari EtherNAT - add writew_be for data push

Hi Geert, as you've probably noticed, my previous EtherNAT patch does not compile without this one being applied as well. Comments welcome (is there anyone on this list with access to an EtherNAT card, besides cts and myself?). Regarding performance afforded by having a 100 Mbit PHY instead of