Date: Fri, 4 Jul 2008 12:21:25 +1000 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Ed Schouten <ed@80386.nl> Cc: FreeBSD Arch <arch@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: MPSAFE TTY schedule Message-ID: <20080704022125.GA32475@server.vk2pj.dyndns.org> In-Reply-To: <20080703205220.GW14567@hoeg.nl> References: <20080702190901.GS14567@hoeg.nl> <20080703193406.GS29380@server.vk2pj.dyndns.org> <20080703205220.GW14567@hoeg.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
--45Z9DzgjV8m4Oswq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Ed, Thanks for your response. On 2008-Jul-03 22:52:20 +0200, Ed Schouten <ed@80386.nl> wrote: >Well, even though I'd rather let other people assess me, I think I've >been very proactive so far. As you can see, I sent my email to the list >two days ago. In those two days I've fixed both umodem(4) and uftdi(4) >to work with the new TTY layer again. And I don't expect you to do all the work yourself - you can't be expected to test hardware you don't have. But where is the documentation to let someone else adapt the drivers? >> cy(4), digi(4), rp(4), rc(4), si(4). > >Who actually owns one of these devices? If you do, please contact me. If >I didn't make myself clear enough: I *am* willing to (assist in >porting|port) these drivers. I have access to a Digi Xem boards at work and have poked around inside the digi(4) code in the past. My difficulty is that the cards are all in use and upgrading to a FreeBSD-current that doesn't support them and then porting the driver is probably not an option (whereas converting it from using shims to access the TTY layer to doing so directly would probably be acceptable - because I can get the board going again in a hurry if needed). I can't help with any of the others, sorry. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --45Z9DzgjV8m4Oswq Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkhtiSUACgkQ/opHv/APuIcPxACgoXjGnN5twMkRBUf63f+nXmMJ S8wAoIpB4WxR0j4p/+KJOwJqeFZmtNQc =9A2i -----END PGP SIGNATURE----- --45Z9DzgjV8m4Oswq--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080704022125.GA32475>