linux-kernel - Re: [PATCH] m68k: defconfig: Update defconfigs for v5.4-rc1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20191105203620.GA12862@allandria.com>
Date:   Tue, 5 Nov 2019 12:36:21 -0800
From:   Brad Boyer <flar@...andria.com>
To:     Finn Thain <fthain@...egraphics.com.au>
Cc:     John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>,
        Geert Uytterhoeven <geert@...ux-m68k.org>,
        Max Staudt <max@...as.org>,
        linux-m68k <linux-m68k@...ts.linux-m68k.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        linux-ide@...r.kernel.org
Subject: Re: [PATCH] m68k: defconfig: Update defconfigs for v5.4-rc1

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@...andria.com