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]
Date:	Sat, 2 Jun 2012 08:54:25 +0200
From:	Jean Delvare <khali@...ux-fr.org>
To:	Meelis Roos <mroos@...ux.ee>
Cc:	Geert Uytterhoeven <geert@...ux-m68k.org>,
	Dean Nelson <dnelson@...hat.com>,
	Linux Kernel list <linux-kernel@...r.kernel.org>
Subject: Re: f71805f arch dependencies?

On Sat, 2 Jun 2012 09:27:51 +0300 (EEST), Meelis Roos wrote:
> > > Indeed, it seems commit 746cdfbf01c0a30d59f6e1b6942d432658d7c7cd
> > > ("hwmon: Avoid building drivers for powerpc that read/write ISA addresses")
> > > was a bit too limited...
> > 
> > I am fine extending that commit to other architectures. Now the
> > question is, do we just add SPARC64 to the exception list, or do we
> > restrict these drivers to X86? I know they are mostly used on X86, but
> > I have no proof they aren't used on other architectures. That's why
> > Dean and myself decided to play it safe at first and only exclude PPC.
> > 
> > Apparently other drivers (e.g. watchdog drivers) for similar chips are
> > limited to X86 so we might as well do the same here. And see if anybody
> > complains...
> > 
> > Meelis, do you feel like sending a patch, or do you prefer if I take
> > care of it?
> 
> I can send a patch in a couple of days, but I do not know either wihich 
> way is better.
> 
> What other architectures can use the ISA-IO style LPC - probably quite 
> several if hardware has been made (but it probably hasn't)?

I just don't know, this is the problem.

-- 
Jean Delvare
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ