Date: Fri, 16 Nov 2012 11:03:59 -0700 From: Warner Losh <imp@bsdimp.com> To: Adrian Chadd <adrian@freebsd.org> Cc: "Rodney W. Grimes" <freebsd@pdx.rh.cn85.chatusa.com>, freebsd-mips@freebsd.org Subject: Re: heads up - changing uart -> uart_ar71xx Message-ID: <8C61D434-FD1A-4DA2-BD5B-C7EBD6685A60@bsdimp.com> In-Reply-To: <CAJ-Vmo=onaX8-or5TskF=-uHcp%2BUR5Ne0fSSrd8fs8mNu4dHmA@mail.gmail.com> References: <201211161735.qAGHZb0j070251@pdx.rh.CN85.ChatUSA.com> <6FC455B0-EBF6-4160-A491-A818003262A6@bsdimp.com> <CAJ-Vmo=onaX8-or5TskF=-uHcp%2BUR5Ne0fSSrd8fs8mNu4dHmA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Nov 16, 2012, at 11:03 AM, Adrian Chadd wrote: > On 16 November 2012 10:01, Warner Losh <imp@bsdimp.com> wrote: >>=20 >> On Nov 16, 2012, at 10:35 AM, Rodney W. Grimes wrote: >>=20 >>> This should be cleaned up better than that, what -kind- of uart is = it? >>> There should be things called >>> uart_8250 (should be able to drive everything from 8250 to = 16950) >>> uart_8530 (this is probalby the second most common uart in the = world) >>> uart_6850 (we would probably never see one of these) >>> etc... >>>=20 >>> Please do not lock this to a specific Mips chip if at all possible >>=20 >> uart already services a dozen of other UARTs. It isn't tied to MIPS = at all. All Adrian seems to be doing is making what was automatic = configuration a little more manual. >=20 > Well, strictly speaking yes. But what I'll do later is make a > 'uart_core' and then allow my MIPS platforms to only register the > uart(s) they need. >=20 > Right now it includes all of the uarts in sys/dev/uart/. They're not > separate devices. This must be a mips-specific thing, since on arm you only get what you = ask for. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8C61D434-FD1A-4DA2-BD5B-C7EBD6685A60>