Date: Mon, 20 Feb 2012 14:23:21 +0100 From: "Julian H. Stacey" <jhs@berklix.com> To: Frank Shute <frank@shute.org.uk> Cc: Terrence Koeman <terrence@mediamonks.net>, "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: Which mailinglist is appropriate for discussing uart changes? Message-ID: <201202201323.q1KDNLqN007231@fire.js.berklix.net> In-Reply-To: Your message "Mon, 20 Feb 2012 03:19:32 GMT." <20120220031932.GA66847@orange.esperance-linux.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Frank Shute wrote: > On Sun, Feb 19, 2012 at 07:10:30PM +0100, Terrence Koeman wrote: > > > > Could someone point me to the right mailinglist to discuss adding > > support for the MCS9904 chip to uart? I'm working on it, but I have > > some questions regarding FIFO sizes and how they are currently > > determined. > >=20 > > Thanks. > >=20 > > -- Regards, T. Koeman, MTh/BSc/BPsy; Technical Monk > > Hi Terrence, > > Looking at the list of mailing lists, I'd say your best bet is to send > an e-mail to freebsd-net@ asking them if it's appropriate to ask the > question there and if not where. > > uarts and FIFOs sounds like it's network stack to me and I'd guess > someone on that list might be able to supply you with an answer. No, net@ is net protocols. Getting a new uart working is driver work, for that http://lists.freebsd.org/mailman/listinfo shows (though I'm not familiar with that list) http://lists.freebsd.org/mailman/listinfo/freebsd-drivers As fallback, try hackers@ for normal developing based on a release, or current@ if you want more developers on the bleeding edge. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below not above, cumulative like a play script, & indent with "> ". Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. Mail from @yahoo dumped @berklix. http://berklix.org/yahoo/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201202201323.q1KDNLqN007231>