Re: armv7 and unified TLBs

> Date: Wed, 3 Aug 2016 10:34:08 +1000 > From: Jonathan Gray > > On Tue, Aug 02, 2016 at 01:43:10PM +0200, Mark Kettenis wrote: > > > Date: Tue, 2 Aug 2016 02:02:57 +1000 > > > From: Jonathan Gray > > > > Adding back tech@ just in case a knwoledgable person

grab global lock during acpi_powerdown

Hi, I was looking at fixing powerdown on the x260 Skylake machine and ran into the EC XXX comment from acpi_powerdown(). I think that grabbing the global lock before doing the AML calls is a good start. What we are missing now is incrementing the global_lock_count variable from the ACPI thread

Re: grab global lock during acpi_powerdown

> Date: Wed, 3 Aug 2016 13:22:33 +0300 > From: Paul Irofti > > Hi, > > I was looking at fixing powerdown on the x260 Skylake machine and ran > into the EC XXX comment from acpi_powerdown(). > > I think that grabbing the global lock before doing the AML calls is a > good start.

Re: quiet legacy drivers on amd64

> Can't speak for clock. But I tend to not like this for nvram. > IMHO, even with recent HW this is a valid concern and reminder > that someone should handle setting of the nvram options correctly. I don't think that is the case. It seems many modern vendors don't perform the checksum.

Re: C startup code: make crtbegin code safe for clang

Philip Guenther wrote: > On Mon, Aug 1, 2016 at 11:45 AM, Mark Kettenis > wrote: > >> From: j...@wxcvbn.org (Jeremie Courreges-Anglas) > >> Date: Mon, 01 Aug 2016 20:30:33 +0200 > >> > >> Stefan Kempf writes: > >> > >> > The constructor and

Re: arm: replace sxiuart with com(4)

Can the iir read be after the tty check, or must it be before?

arm: replace sxiuart with com(4)

Hi, the Synopsys Designware UART, which is used on a bunch of SoCs, is mostly compatible to com(4). Currently we use sxiuart, a driver based on another driver, modified to work on sunxi. I would like to replace sxiuart with com(4). This diff disables sxiuart and implements the Allwinner and

Re: arm: replace sxiuart with com(4)

On Wed, Aug 03, 2016 at 02:56:53PM -0600, Theo de Raadt wrote: > Can the iir read be after the tty check, or must it be before? > When I did that diff initially I had the read and busy check after the sc->sc_tty check. The hardware I created this diff for has a shared interrupt line for two

Re: arm: replace sxiuart with com(4)

> Date: Wed, 3 Aug 2016 22:36:02 +0200 > From: Patrick Wildt > > Hi, > > the Synopsys Designware UART, which is used on a bunch of SoCs, is > mostly compatible to com(4). Currently we use sxiuart, a driver based > on another driver, modified to work on sunxi. I would like

Re: arm: replace sxiuart with com(4)

> I don't think the com(4) part of the diff is quite right. This busy > indicator feature seems to be specific to the Designware core. I > can't find the original NS16750 datasheet (was there ever one?), but > it isn't present on any of the true 16750 clones. So I think that > instead of adding

Re: arm: replace sxiuart with com(4)

On Wed, Aug 03, 2016 at 03:33:21PM -0600, Theo de Raadt wrote: > > I don't think the com(4) part of the diff is quite right. This busy > > indicator feature seems to be specific to the Designware core. I > > can't find the original NS16750 datasheet (was there ever one?), but > > it isn't

Re: arm: replace sxiuart with com(4)

> > Patrick send me a newer version of the diff with better documentation. > > > > And that makes the same is clear to me. At least one of these flags > > should be changed to make sure it is narrowly specific to this > > particular defective chip implementation. > > > > > The comments should