From: Finn Thain <fthain@telegraphics.com.au>
To: Michael Schmitz <schmitzmic@googlemail.com>
Cc: Thorsten Glaser <tg@mirbsd.de>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k@vger.kernel.org
Subject: Re: Debian kernel v2.6.38
Date: Mon, 25 Apr 2011 13:53:05 +1000 (EST) [thread overview]
Message-ID: <alpine.OSX.2.00.1104251301580.196@ibook.intranet> (raw)
In-Reply-To: <4DB4E109.3090809@gmail.com>
On Mon, 25 Apr 2011, Michael Schmitz wrote:
> Finn Thain wrote:
> > On Sat, 23 Apr 2011, Thorsten Glaser wrote:
> >
> >
> > > No idea about the required status of the other patches, e.g. Mac.
> > > Finn?
> > >
> >
> > Most of the relevant mac patches were merged into the mainline prior
> > to the 2.6.34 release and by 2.6.37 all of them were merged.
> >
> > I do have some unfinished patches based on 2.6.37 but I'm pretty sure
> > they don't relate to the mac hardware used by the Debian/68k
> > developers.
> >
> Incidentially - did you work on the Mac 5380 SCSI code recently? Does it
> work with full error handling capability in its current state?
I got as far as confirming the reports of working mac_scsi on the IIfx. It
fails on every other model. I didn't really investigate error handling.
The explanation was that PDMA isn't relevant to the IIfx so the driver
runs in PIO mode (should be DMA but that has not yet been implemented
successfully).
>
> I begin to feel the only way to make the Falcon SCSI code work again is
> a clean restart ...
That was also my feeling when we discussed this some years ago*.
I'm told that mac_scsi PDMA worked for either mac68k or mainline 2.2
kernels and so I tend to think that a rewrite would likely suffer from the
same PDMA bug. I really need to investigate that bug.
There are still good reasons for a rewrite but I don't have the necessary
understanding of the SCSI subsystem nor the time to tackle those issues.
But if someone else were to rewrite the core 5380 driver as was done with
esp_scsi.c then I would be willing to tackle the mac portion (the
equivalent of mac_esp.c)...
Finn
* http://thread.gmane.org/gmane.linux.scsi/44873
>
> Cheers,
>
> Michael
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2011-04-25 3:52 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-23 18:00 Debian kernel v2.6.38 (was: Re: Fix for SLUB?) Geert Uytterhoeven
2011-04-23 18:13 ` Debian kernel v2.6.38 Thorsten Glaser
2011-04-23 19:19 ` Geert Uytterhoeven
2011-04-23 19:58 ` Thorsten Glaser
2011-04-23 22:12 ` Michael Schmitz
2011-04-24 8:18 ` Geert Uytterhoeven
2011-04-24 11:37 ` Thorsten Glaser
2011-04-25 2:36 ` Michael Schmitz
2011-04-25 14:19 ` Thorsten Glaser
2011-04-25 1:33 ` Thorsten Glaser
2011-04-24 16:18 ` Finn Thain
2011-04-25 2:48 ` Michael Schmitz
2011-04-25 3:53 ` Finn Thain [this message]
2011-04-29 23:44 ` Michael Schmitz
2011-05-08 12:58 ` Debian kernel 2.6.38-5 Thorsten Glaser
2011-05-08 16:59 ` Christian T. Steigies
2011-05-08 18:00 ` Geert Uytterhoeven
2011-05-08 18:49 ` Thorsten Glaser
2011-05-08 19:26 ` Geert Uytterhoeven
2011-05-08 18:40 ` Thorsten Glaser
2011-05-08 20:08 ` Christian T. Steigies
2011-05-08 20:22 ` Geert Uytterhoeven
2011-05-08 20:58 ` Michael Schmitz
2011-05-08 21:45 ` Christian T. Steigies
2011-05-08 21:30 ` Thorsten Glaser
2011-05-08 23:14 ` Finn Thain
2011-05-09 7:16 ` Geert Uytterhoeven
2011-05-09 20:25 ` Christian T. Steigies
2011-05-09 22:49 ` Michael Schmitz
2011-05-10 7:00 ` Christian T. Steigies
2011-05-10 7:38 ` Michael Schmitz
2011-05-09 20:28 ` zorro8390 (was: Re: Debian kernel 2.6.38-5) Geert Uytterhoeven
2011-05-10 9:01 ` Debian kernel 2.6.38-5 Geert Uytterhoeven
2011-05-10 11:57 ` Finn Thain
2011-05-10 12:06 ` Geert Uytterhoeven
2011-05-08 20:53 ` 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=alpine.OSX.2.00.1104251301580.196@ibook.intranet \
--to=fthain@telegraphics.com.au \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=schmitzmic@googlemail.com \
--cc=tg@mirbsd.de \
/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