linux-m68k.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Kars de Jong <jongk@linux-m68k.org>
Cc: Andreas 'count' Kotes 
	<count-vger.kernel.org+linux-m68k@flatline.de>,
	linux-m68k <linux-m68k@vger.kernel.org>
Subject: Re: Amiga PCMCIA network card support
Date: Mon, 28 Oct 2019 12:08:07 +0100	[thread overview]
Message-ID: <1989702b-16ca-b376-c33d-9e04e6de2ca3@physik.fu-berlin.de> (raw)
In-Reply-To: <CACz-3riJHfuhkFMyPbUCz8Q9Mbu6T+CFz5gMwAKzMeg0tjM4Hg@mail.gmail.com>

Hi Kars!

On 10/28/19 10:19 AM, Kars de Jong wrote:
>>> Then Real Life happened and I didn't touch my Amiga for 10+ years...
>>
>> .. hmm, is this something that's likely to change? ;)
> 
> I've dusted it off and powered it on this weekend. It still works (RTC
> needs a new battery though), and the 2.6.18 kernel that I modified
> many years ago still works fine with the pcnet_cs driver and my
> Dynalink L10C card.

Cool!

> I then tried a build of master of Geert's tree, which unfortunately
> doesn't fully work due to issues with the Blizzard ESP driver. I also

Could you report these issues? Is it the zorro_esp driver that's causing
problems? Normally the kernel should build fine but if there are issues,
Michael Schmitz would probably be interested to hear about them.

> had similar issues with the last 2.6.2x kernel I tested in 2008(?),
> after switching to the new ESP driver.
> The drive is identified, set to synchronous 10 MHz mode, some
> transfers are done but then it locks up. After the ESP driver runs its
> recovery procedure, the bash that I run as init process exits with
> code 4.

Wait, do you have build issues or do you have issues running the driver?

The new zorro_esp has seen a lot of rewrite. So old bugs might have been
fixed now.

>> Kars, you sound like you're in Europe - will you be on the Chaos
>> Communcation Congress in Leipzig this year? Will there be a Linux m68k
>> table?
> 
> Yes, I'm from Hengelo (the Netherlands), but no, I won't be attending.
> I have no idea whether there will be a Linux/m68k presence.

I don't think there will be any m68k folk at CCC, I'm also not attending
as the event has become too political for my taste.

But I will be attending FOSDEM and Geert is coming as well (at least he
has been to every FOSDEM so far ;)), so we can maybe have a small m68k
meeting. I'm coming with two friends who are also Linux hackers.

>> I don't know how well bounties (like
>> https://www.bountysource.com/issues/80706251-m68k-convert-the-backend-to-mode_cc-so-it-can-be-kept-in-future-releases)
>> work, but I'd certainly willing to chip in with money, time and
>> resources to get this addressed for good.
> 
> I don't need money, I need time :-) I looked at the changes I made to
> 2.6.18, most of it is pretty self contained and should still work on
> 5.x without too many changes, but the io.h changes are more hairy.
> Also, someone once tested this on his A1200 which had a 68030 and I
> believe it broke. Something about ioremap() not accepting physical
> addresses that were already mapped by a fixed mapping (Zorro II
> address space).

Doesn't this depend on the type of accelerator used? I think some of them
cause incompatibilities with the PCMCIA slot, don't they?

>> I think cleaning up the IRQ handling etc would also be (another?) good
>> showcase of linux-m68k and the Amiga platform being very much alive,
>> contrary to what Linus might think :D
> 
> Linus knows it's alive, he just seems to wonder why it won't die ;-)

Because the Amiga community is absolutely die-hard :). This year's Amiga
conference was even extended to two days because of the public interest.

> I will try to prepare a patch for the IRQ handling.

Nice. Thank you! Really cool to see more and more people starting to work
on Linux/m68k again :). This shows that all the effort I put into Debian/m68k
was worth it!

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz@debian.org
`. `'   Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

  reply	other threads:[~2019-10-28 11:08 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-24 20:56 Amiga PCMCIA network card support Andreas 'count' Kotes
2019-10-25  7:25 ` Kars de Jong
2019-10-25 11:49   ` Andreas 'count' Kotes
2019-10-28  9:19     ` Kars de Jong
2019-10-28 11:08       ` John Paul Adrian Glaubitz [this message]
2019-10-28 13:00         ` Kars de Jong
2019-10-28 13:20           ` John Paul Adrian Glaubitz
2019-10-28 15:39             ` ESP SCSI driver (was: Amiga PCMCIA network card support) Kars de Jong
2019-10-28 18:32               ` Michael Schmitz
2019-10-29  9:37                 ` Kars de Jong
2019-10-29 20:20                   ` ESP SCSI driver Michael Schmitz
2019-10-29 22:05                   ` [PATCH] esp_scsi: Add support for FSC chip Kars de Jong
2019-10-30  0:23                     ` Michael Schmitz
2019-10-30  7:11                       ` Kars de Jong
2019-10-30 18:42                         ` Michael Schmitz
2019-10-30  0:31                     ` Finn Thain
2019-10-30  1:06                       ` Michael Schmitz
2019-10-30  7:25                         ` Kars de Jong
2019-10-30  8:45                           ` Geert Uytterhoeven
2019-10-30  9:08                             ` Kars de Jong
2019-10-30 18:34                               ` Michael Schmitz
2019-10-30 18:52                             ` Brad Boyer
2019-10-30  7:22                       ` Kars de Jong
2019-10-30 23:15                         ` Finn Thain
2019-11-12 18:57                     ` [PATCH 0/2] Some esp_scsi updates Kars de Jong
2019-11-12 18:57                       ` [PATCH 1/2] esp_scsi: Correct ordering of PCSCSI definition in esp_rev enum Kars de Jong
2019-11-12 23:07                         ` Finn Thain
2019-11-13  8:00                           ` Kars de Jong
2019-11-13 22:25                             ` Finn Thain
2019-11-13 14:22                         ` Christoph Hellwig
2019-11-13 15:03                           ` Kars de Jong
2019-11-12 18:57                       ` [PATCH 2/2] esp_scsi: Add support for FSC chip Kars de Jong
2019-11-12 23:18                         ` Finn Thain
2019-11-12 23:57                           ` Finn Thain
2019-11-13  9:30                           ` Kars de Jong
2019-11-13 22:24                             ` Finn Thain
2019-11-14 21:59                       ` [PATCH v2 0/2] Some esp_scsi updates Kars de Jong
2019-11-14 21:59                         ` [PATCH 1/2] esp_scsi: Correct ordering of PCSCSI definition in esp_rev enum Kars de Jong
2019-11-14 22:06                           ` Kars de Jong
2019-11-14 21:59                         ` [PATCH 2/2] esp_scsi: Add support for FSC chip Kars de Jong
2019-11-14 22:07                           ` Kars de Jong
2019-11-14 22:25                         ` [PATCH v3 0/2] Some esp_scsi updates Kars de Jong
2019-11-14 22:25                           ` [PATCH v2 1/2] esp_scsi: Correct ordering of PCSCSI definition in esp_rev enum Kars de Jong
2019-11-15  2:13                             ` Finn Thain
2019-11-15  7:04                               ` Kars de Jong
2019-11-14 22:25                           ` [PATCH v3 2/2] esp_scsi: Add support for FSC chip Kars de Jong
2019-11-15  2:09                             ` Finn Thain
2019-11-18 13:27                               ` Kars de Jong
2019-11-09 19:14                   ` [PATCH] zorro_esp: increase maximum dma length to 65536 bytes Kars de Jong
2019-11-09 20:12                     ` James Bottomley
2019-11-10  2:36                       ` Michael Schmitz
2019-11-10  9:01                         ` Kars de Jong
2019-11-10 19:26                           ` Michael Schmitz
2019-11-11  8:47                             ` Kars de Jong
2019-11-10 19:35                         ` James Bottomley
2019-11-12 17:55                           ` [PATCH v2] zorro_esp: Limit DMA transfers to 65536 bytes (except on Fastlane) Kars de Jong
2019-11-12 22:46                             ` Finn Thain
2019-11-13  2:27                             ` Martin K. Petersen
2019-11-12  9:34                         ` [PATCH] zorro_esp: increase maximum dma length to 65536 bytes Kars de Jong
2019-11-09 22:53                     ` Finn Thain
2019-11-10  9:06                       ` Kars de Jong
2019-10-28 23:38               ` ESP SCSI driver (was: Amiga PCMCIA network card support) Finn Thain
2019-10-29 11:52                 ` Kars de Jong
2019-10-29 20:16                   ` ESP SCSI driver Michael Schmitz
2019-10-28 22:31           ` Amiga PCMCIA network card support Finn Thain
2019-10-29  8:56           ` FOSDEM (was: Re: Amiga PCMCIA network card support) Geert Uytterhoeven
2019-10-29  9:13             ` John Paul Adrian Glaubitz
2019-10-28 22:08       ` Amiga PCMCIA network card support Finn Thain
2019-10-29  9:00       ` Geert Uytterhoeven
2019-10-29  9:12         ` John Paul Adrian Glaubitz
2019-10-29  9:14           ` Geert Uytterhoeven
2019-10-29  9:20             ` John Paul Adrian Glaubitz
2019-10-29  9:40         ` Kars de Jong
2019-10-28  6:57   ` Michael Schmitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1989702b-16ca-b376-c33d-9e04e6de2ca3@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=count-vger.kernel.org+linux-m68k@flatline.de \
    --cc=jongk@linux-m68k.org \
    --cc=linux-m68k@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).