Committing a driver to -stable

[Bosko Milekic]

On Fri, Jul 18, 2003 at 06:19:46PM +0200, Harti Brandt wrote:
> 
> Hi all,
> 
> as far as I know new stuff should be first committed to -current and, if
> it turns out stable enough, MFCed to -stable. I would like to commit a
> driver to -stable that will not be in -current. The driver is for ProSum's
> ProATM card. I have recently committed a full busdma driver to current
> (patm(4)), that I hesitate to backport to -stable because it requires ATM
> infrastructure that we don't have in stable. On the other hand there is a
> -stable driver for this card from ProSum (www.prosum.fr) that is reported
> to be very stable under -stable :-), that several people use and that I
> would like to commit. So, can I do this?
> 
> harti
> -- 
> harti brandt,
> http://www.fokus.fraunhofer.de/research/cc/cats/employees/hartmut.brandt/private
> brandt at fokus.fraunhofer.de, harti at freebsd.org

  If the same device is supported under -current already, and it's a
  question of how the driver is implemented (i.e., completely
  differently in -stable due to a lack of -current's ATM
  infrastructure), then I don't see why not.  However, you may want to
  wait for someone from the TRB (is there a list of who's part of this
  group somewhere, anyway?) and/or -core to respond before you take
  action.

-- 
Bosko Milekic  *  bmilekic at technokratis.com  *  bmilekic at FreeBSD.org
TECHNOkRATIS Consulting Services  *  http://www.technokratis.com/