Am 15.02.19 um 21:28 schrieb Warner Losh:
> On Fri, Feb 15, 2019 at 12:54 PM Ian Lepore wrote:
>
>> On Fri, 2019-02-15 at 12:32 -0700, Warner Losh wrote:
>>> On Fri, Feb 15, 2019 at 12:17 PM Ian Lepore wrote:
>> I guess the question would be how many things does '...' represent now
>> and in the
On Fri, Feb 15, 2019 at 12:54 PM Ian Lepore wrote:
> On Fri, 2019-02-15 at 12:32 -0700, Warner Losh wrote:
> > On Fri, Feb 15, 2019 at 12:17 PM Ian Lepore wrote:
> >
> > > On Fri, 2019-02-15 at 10:53 -0800, Enji Cooper wrote:
> > > > > [...]
> > > >
> > > > HO Eric!
> > > >
> > > > iflib was a r
ifdi_if.h is a system generated interface file that network drivers that
depend on iflib use. It's generated from ifdi_if.m in sys/net.
My guess is that you don't have "device iflib" defined in your kernel
configuration. em(4) depends on iflib in FreeBSD 12/13, and with r343617,
iflib is now expli
On Fri, 2019-02-15 at 12:32 -0700, Warner Losh wrote:
> On Fri, Feb 15, 2019 at 12:17 PM Ian Lepore wrote:
>
> > On Fri, 2019-02-15 at 10:53 -0800, Enji Cooper wrote:
> > > > [...]
> > >
> > > HO Eric!
> > >
> > > iflib was a recently added requirement on stable/12 IIRC..?
> > >
> > > Does the
Lev Serebryakov writes:
> > My question would be: why? If some drivers have a new
> > dependency on iflib, why isn't that expressed in sys/conf/files
> > and handled automatically?
>
> My question exactly.
I am so glad people who know what they're talking about have the
same resp
On Fri, Feb 15, 2019 at 12:17 PM Ian Lepore wrote:
> On Fri, 2019-02-15 at 10:53 -0800, Enji Cooper wrote:
> > > On Feb 15, 2019, at 10:46, Eric Joyner wrote:
> > >
> > > ifdi_if.h is a system generated interface file that network drivers
> > > that depend on iflib use. It's generated from ifdi_
On 15.02.2019 21:59, Ian Lepore wrote:
> My question would be: why? If some drivers have a new dependency on
> iflib, why isn't that expressed in sys/conf/files and handled
> automatically?
My question exactly.
--
// Lev Serebryakov
signature.asc
Description: OpenPGP digital signature
On Fri, 2019-02-15 at 10:53 -0800, Enji Cooper wrote:
> > On Feb 15, 2019, at 10:46, Eric Joyner wrote:
> >
> > ifdi_if.h is a system generated interface file that network drivers
> > that depend on iflib use. It's generated from ifdi_if.m in sys/net.
> >
> > My guess is that you don't have "dev
Looking through the SVN logs, it looks like kib put an entry in the
stable/12 UPDATING in r344149 when he MFC'd the "make iflib a loadable
module" changes.
As for the em man page, they don't note the specific "device iflib"
dependency, so that needs to be added (as well as a more general update
si
> On Feb 15, 2019, at 10:46, Eric Joyner wrote:
>
> ifdi_if.h is a system generated interface file that network drivers that
> depend on iflib use. It's generated from ifdi_if.m in sys/net.
>
> My guess is that you don't have "device iflib" defined in your kernel
> configuration. em(4) depen
On Fri, Feb 15, 2019 at 09:50:55AM +0200, Andriy Gapon wrote:
>
> So, I suspect something exotic like some sort of a stack alignment issue, or a
> CPU bug, or a mismatch between object files, or some local experiment, etc.
>
You might be right about something exotic. It is an old
laptop, so it
On Thu, Feb 14, 2019 at 04:24:28PM -0500, Robert Huff wrote:
>
> On a system running:
>
> FreeBSD 13.0-CURRENT r343080 amd64
>
> with source tree updated at midnight last night, attempts to
> build a kernel with "device em" die with:
Did you added 'device iflib' to your kernel confi
12 matches
Mail list logo
