From owner-freebsd-arm@FreeBSD.ORG Thu Jan 22 17:24:38 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E07985D4 for ; Thu, 22 Jan 2015 17:24:38 +0000 (UTC) Received: from mail-pd0-f173.google.com (mail-pd0-f173.google.com [209.85.192.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ADF9F85F for ; Thu, 22 Jan 2015 17:24:38 +0000 (UTC) Received: by mail-pd0-f173.google.com with SMTP id fp1so2834910pdb.4 for ; Thu, 22 Jan 2015 09:24:32 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=qcvlqBsWMxhRrfO5waBDw12RouYVNReI/A+nHt34Ovk=; b=fh+TYCHpLM6IRBf82fpE18nV8+rBVVoyRW+Pam5rrI27FwO+h+yC31SsLNUx5jYzPg FgWeo5WGVEUZW/E0up7qHLDr82VO39rZUWUFNiMS1QpK2rmmdY1L6vs84AQUAeNE+gYf bcBlKcYp2e9qozh2pSnoCqAvKeQffKo8rFM8iab6kmj9QLU3VU9+eqMVmkg0cmYPiNLA 2G5PnL5nfr0pKn5MC0bv+znOR7qK2n1VMoQ3oH0tRZTnjbGUEAA49sBzuOHCiHyqJc5H z80QYAiP5bxW6v8kQ0yOo0ajofWRJHttAxV9SN7FMHAkJcVqjVxMFTVcNg1FsbzvkZ32 2wcA== X-Gm-Message-State: ALoCoQl/DCVSxS2DEhHg0Gnj12mK3zSmCaInzHpx6sIhsJSQ+UzQdqhv6gXjM8GPo0VfcRE5UqFD X-Received: by 10.66.222.135 with SMTP id qm7mr4041618pac.38.1421946976859; Thu, 22 Jan 2015 09:16:16 -0800 (PST) Received: from bsdimp.corp.netflix.com ([69.53.237.72]) by mx.google.com with ESMTPSA id jd1sm9474350pbd.49.2015.01.22.09.16.15 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 22 Jan 2015 09:16:16 -0800 (PST) Sender: Warner Losh Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: interrupt framework From: Warner Losh In-Reply-To: <20150122101213.5b0f6aea@bender.lan> Date: Thu, 22 Jan 2015 10:16:15 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <54BA9888.1020303@freebsd.org> <54BD3F86.3010901@freebsd.org> <54BD9794.4080204@freebsd.org> <54BE7E6D.6060800@freebsd.org> <20150121180916.110fc8ad@bender.lan> <74044D4B-A841-48E0-88CD-73B659454B86@bsdimp.com> <20150122101213.5b0f6aea@bender.lan> To: Andrew Turner X-Mailer: Apple Mail (2.1993) Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2015 17:24:39 -0000 > On Jan 22, 2015, at 3:12 AM, Andrew Turner = wrote: >=20 > On Wed, 21 Jan 2015 16:32:47 -0700 > Warner Losh wrote: >>> On Jan 21, 2015, at 11:09 AM, Andrew Turner >>> wrote: >>>=20 >>> On Wed, 21 Jan 2015 10:50:14 -0700 >>> Warner Losh wrote: >>>> =E2=80=9Cusually=E2=80=9D? I thought it was always 100%: We=E2=80=99r= e wither using FDT or >>>> we=E2=80=99re not. Some platforms allow compiling for both (mostly = as a >>>> transition aid to FDT), but I=E2=80=99m not aware of any that would = be a >>>> mix. >>>=20 >>> There may be a case on arm64 to use both fdt and ACPI. In this case >>> it would be used as a transition to add support for ACPI as some >>> hardware may require it. >>=20 >> Speaking of ACPI, will/can arm64 use UEFI? The two seem to be joined >> at the hip these days=E2=80=A6 >=20 > On servers I expect UEFI to be used. For more embedded devices, e.g. > phones or tablets, the boot environment will be less standardised. So it would be useful that any UEFI work from user land be architected = to potentially support arm64? I=E2=80=99m thinking =E2=80=9Cyes=E2=80=9D. Warner