linux-kernel - Re: [PATCH] enable readback to get HPET working on ATI SB4x00, kernel 2.6.35

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LFD.2.00.1007151011550.3321@localhost.localdomain>
Date:	Thu, 15 Jul 2010 10:22:14 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Stephan Wolf <stephan@...zte-bankreihe.de>
cc:	Borislav Petkov <borislav.petkov@....com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Herrmann3, Andreas" <Andreas.Herrmann3@....com>
Subject: Re: [PATCH] enable readback to get HPET working on ATI SB4x00, kernel
 2.6.35_rc5

On Thu, 15 Jul 2010, Stephan Wolf wrote:
> Am 14.07.2010 23:04, schrieb Thomas Gleixner:
> 
> > +static void __init ati_hpet_bugs(int num, int slot, int func)
> > +{
> > +#ifdef CONFIG_HPET_TIMER
> > +	hpet_readback_cmp = 1;
> > +#endif
> > +}
> > +
> >   #define QFLAG_APPLY_ONCE 	0x1
> >   #define QFLAG_APPLIED		0x2
> >   #define QFLAG_DONE		(QFLAG_APPLY_ONCE|QFLAG_APPLIED)
> > @@ -220,6 +236,8 @@ static struct chipset early_qrk[] __init
> >   	  PCI_CLASS_SERIAL_SMBUS, PCI_ANY_ID, 0, ati_bugs },
> >   	{ PCI_VENDOR_ID_ATI, PCI_DEVICE_ID_ATI_SBX00_SMBUS,
> >   	  PCI_CLASS_SERIAL_SMBUS, PCI_ANY_ID, 0, ati_bugs_contd },
> > +	{ PCI_VENDOR_ID_ATI, PCI_ANY_ID,
> > +	  PCI_CLASS_SERIAL_SMBUS, PCI_ANY_ID, 0, ati_hpet_bugs },
> >   	{}
> 
> Hi, the patch above solves the problem on my machine.

Thanks for testing. 

Borislav, any opinion ?

Thanks,

	tglx
--
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/