On Tue, May 18, 2010 at 02:07:33PM -0400, John Baldwin wrote:
> On Tuesday 18 May 2010 1:30:32 pm Pyun YongHyeon wrote:
> > On Tue, May 18, 2010 at 01:15:37PM -0400, John Baldwin wrote:
> > > I think it would be useful if we could pick a device-independent
> > > interface for
> > > configuring fl
On Tuesday 18 May 2010 1:30:32 pm Pyun YongHyeon wrote:
> On Tue, May 18, 2010 at 01:15:37PM -0400, John Baldwin wrote:
> > I think it would be useful if we could pick a device-independent interface
> > for
> > configuring flow control on network interfaces, perhaps as media options
> > via
> >
On Tuesday 18 May 2010 1:30:32 pm Pyun YongHyeon wrote:
> On Tue, May 18, 2010 at 01:15:37PM -0400, John Baldwin wrote:
> > I think it would be useful if we could pick a device-independent interface
for
> > configuring flow control on network interfaces, perhaps as media options
via
> > ifconfi
On Tue, May 18, 2010 at 01:15:37PM -0400, John Baldwin wrote:
> I think it would be useful if we could pick a device-independent interface
> for
> configuring flow control on network interfaces, perhaps as media options via
> ifconfig. I know that the msk(4) driver allows RX and TX flow control
I think it would be useful if we could pick a device-independent interface for
configuring flow control on network interfaces, perhaps as media options via
ifconfig. I know that the msk(4) driver allows RX and TX flow control to be
toggled via the link0 and link1 flags (the manpage for msk(4) n
