Messages in this thread | | | Date | Mon, 9 Jul 2012 14:06:29 +0100 | From | Matthew Garrett <> | Subject | Re: [PATCH 00/36] AArch64 Linux kernel port |
| |
On Mon, Jul 09, 2012 at 01:32:56PM +0100, Mark Brown wrote:
> If you end up having to write two whole drivers that sounds enormously > depressing especially for those of us working on devices that aren't > architecture specific. We've managed to avoid that thus far with device > tree and platform data, would it not be possible to mandate that people > use ACPI in a vaugley sane way which can support this too?
There's ongoing discussion about unifying ACPI and ftd representation, and once that's done this isn't a problem, but right now there's no terribly straightforward way to do this without a lot of basically boilerplate code. The biggest issue is that ACPI has a very different idea about event delivery and we'd need some way to abstract that.
-- Matthew Garrett | mjg59@srcf.ucam.org
| |