Linux-ide Archive on lore.kernel.org
 help / color / Atom feed
From: Brad Boyer <flar@allandria.com>
To: Finn Thain <fthain@telegraphics.com.au>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Max Staudt <max@enpas.org>,
	linux-m68k <linux-m68k@lists.linux-m68k.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-ide@vger.kernel.org
Subject: Re: [PATCH] m68k: defconfig: Update defconfigs for v5.4-rc1
Date: Tue, 5 Nov 2019 12:36:21 -0800
Message-ID: <20191105203620.GA12862@allandria.com> (raw)
In-Reply-To: <alpine.LNX.2.21.1.1911051444570.160@nippy.intranet>

On Tue, Nov 05, 2019 at 03:13:31PM +1100, Finn Thain wrote:
> On Mon, 4 Nov 2019, Brad Boyer wrote:
> > I'll try the PB190 first anyway. It should be easier due to not needing 
> > to setup a monitor. 
> 
> I think you can put the 630 into a standard VESA video mode (with MacOS or 
> Linux) given the right adapter/cable. I have a pin-out somewhere.

I have an adapter. I also own several official Apple monitors of various
styles and capabilities. The problem is desk space. I need to clean before
I have enough room to setup anything bigger than a laptop.

> > I just took a look at the macide driver, and it appears to do basically
> > nothing other than pass a list of addresses into the core ide code. It's
> > one of the smallest drivers I've ever seen.
> > 
> 
> The fly in the ointment is interrupt handling. There is a theoretical bug. 
> (Though it doesn't seem to hurt in practice.)
> 
> AFAIK the hardware is publicly undocumented and so we need to do 
> experiments like this:
> https://github.com/fthain/linux/commit/01405199e8d05500bf458df690027655f526a7fd
> 
> My suspicion is that macide_clear_irq() does nothing useful. It's not 
> called on a Powerbook 190. Maybe it is needed on a PowerBook 150 and 
> Performa 630, maybe not...

My understanding has always been that Apple was really sloppy with how
the hardware handled interrupts. On many models, you can't actually
block interrupts in a sane fashion. Because of that, you usually have
to shut up the interrupts by talking to the actual device.

I would not be surprised in the slightest to see that register write
do absolutely nothing. It might be more interesting to just disable
the clear function for all models and see if it still works. I don't
have a PB 150 to test that style, but I do have the other two.

> > > But watch out for leaking capacitors and batteries...
> > 
> > I should pull out every machine in my collection and look for those 
> > sorts of issues. None of them have been checked in at least 5 or 6 
> > years.
> > 
> 
> None of the machines in my collection have any batteries now. Desoldering 
> the Ni-Cd PRAM battery from a Powerbook 14x/16x/170/180 is difficult but 
> necessary. Powerbook 150 and 190 are easier (no desoldering needed).

That makes sense. I need to do the same. It's just a pain since a few
models won't boot without a battery.

	Brad Boyer
	flar@allandria.com


      reply index

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191001073539.4488-1-geert@linux-m68k.org>
2019-10-07 14:11 ` Max Staudt
2019-11-04 11:06   ` Geert Uytterhoeven
2019-11-04 21:15     ` Max Staudt
2019-11-05  0:01     ` Christoph Hellwig
2019-11-05  0:14     ` John Paul Adrian Glaubitz
2019-11-05  0:53       ` Brad Boyer
2019-11-05  2:33         ` Finn Thain
2019-11-05  3:19           ` Brad Boyer
2019-11-05  4:13             ` Finn Thain
2019-11-05 20:36               ` Brad Boyer [this message]

Reply instructions:

You may reply publically 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=20191105203620.GA12862@allandria.com \
    --to=flar@allandria.com \
    --cc=fthain@telegraphics.com.au \
    --cc=geert@linux-m68k.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=max@enpas.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

Linux-ide Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-ide/0 linux-ide/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-ide linux-ide/ https://lore.kernel.org/linux-ide \
		linux-ide@vger.kernel.org
	public-inbox-index linux-ide

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-ide


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git