| 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
| ||
|
Message-ID: <20120222085830.1ed8c25e@pyramind.ukuu.org.uk> Date: Wed, 22 Feb 2012 08:58:30 +0000 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: Tomoya MORINAGA <tomoya.rohm@...il.com> Cc: Darren Hart <dvhart@...ux.intel.com>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Feng Tang <feng.tang@...el.com>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Alan Cox <alan@...ux.intel.com>, linux-serial@...r.kernel.org Subject: Re: [PATCH 0/4] pch_uart: Cleanups, board quirks, and user uartclk parameter > > assume a 192 MHz clock on all boards. The problem with this approach is > > that the CLKCFG register may have been set to something other than the > > 192MHz configuration by the firmware. So you can use the early PCI hooks or even bash the register directly in your early bootup code. You won't be the only early boot console that does this sort of thing. There are even people bitbanging PCI I²C interfaces at boot time for such purpose. > So, I think default uart_clock 192MHz setting is better than Darren's opinion. It's certainly easier to maintain, but it would be good to know if the setting can be written or retrieved directly in the early console setup using the early PCI ops or similar. Alan Alan -- 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