On Nov 13, 7:33am, Jason Thorpe wrote:
} > On Nov 13, 2018, at 7:15 AM, John Nemeth wrote:
} >
} > That's a different kind of unusable. :-) That puts it in
} > the same camp as strip, where there may be functioning hardware,
} > but you can't do anything with the hardware.
}
} ...and
> On Nov 13, 2018, at 7:15 AM, John Nemeth wrote:
>
> That's a different kind of unusable. :-) That puts it in
> the same camp as strip, where there may be functioning hardware,
> but you can't do anything with the hardware.
...and when you can't do anything with the hardware, people
On Nov 13, 7:10am, Martin Husemann wrote:
} On Mon, Nov 12, 2018 at 05:18:41PM -0800, John Nemeth wrote:
} > Was the ISDN code usable? Something in the back of my mind is telling
} > me that it wasn't and thus was just clutter.
}
} It was usable, but even here it is hard (impossible?) to
On Tue, Nov 13, 2018 at 1:26 AM Christos Zoulas wrote:
>
> In article ,
> Greg Troxel wrote:
> >
> >co...@sdf.org writes:
> >
> >> This is an automatically generated list with some hand touchups, feel
> >> free to do whatever with it. I only generated the output.
> >>
> >> ac100ic
> >> acemidi
On Mon, Nov 12, 2018 at 05:18:41PM -0800, John Nemeth wrote:
> Was the ISDN code usable? Something in the back of my mind is telling
> me that it wasn't and thus was just clutter.
It was usable, but even here it is hard (impossible?) to get real ISDN
land lines nowadays.
Martin
On Mon, Nov 12, 2018 at 2:07 PM John Nemeth wrote:
> On Nov 12, 1:16pm, Jason Thorpe wrote:
> } Subject: Re: Things not referenced in kernel configs, but mentioned in
> fil
> } > On Nov 12, 2018, at 11:12 AM, John Nemeth wrote:
> } >
> } > wbsio and wt also seems to fit in that category.
>
On Nov 12, 2:12pm, Jason Thorpe wrote:
} > On Nov 12, 2018, at 1:59 PM, John Nemeth wrote:
} > } On Nov 12, 1:16pm, Jason Thorpe wrote:
} > } > On Nov 12, 2018, at 11:12 AM, John Nemeth wrote:
} > } >
} > } > wbsio and wt also seems to fit in that category.
} > }
} > } Isn't "wt" an
> On Nov 12, 2018, at 1:59 PM, John Nemeth wrote:
>
> On Nov 12, 1:16pm, Jason Thorpe wrote:
> } Subject: Re: Things not referenced in kernel configs, but mentioned in fil
> } > On Nov 12, 2018, at 11:12 AM, John Nemeth wrote:
> } >
> } > wbsio and wt also seems to fit in that
FWIW, it's not a great idea to throw all of the i2c drivers into a kernel what
will ever be booted, because of the i2c address assignment situation.
> On Nov 12, 2018, at 2:15 PM, Brad Spencer wrote:
>
>
> co...@sdf.org writes:
>
>> This is an automatically generated list with some hand
> there's always the Attic
I'm currently using a custom kernel with a driver from netbsd-8
(nouveau), it was surprisingly painless to put the old version in.
(in case anyone is curious, copy sys/external/bsd/{common,drm2}. Of
course, I should attempt to fix it, but I like to be able to run
co...@sdf.org writes:
> This is an automatically generated list with some hand touchups, feel
> free to do whatever with it. I only generated the output.
>
Random ramblings below...
[snip]
> am2315temp
The am2315 will, in theory, work on any reasonable i2c bus, but has only
been tested on a
On Nov 12, 1:16pm, Jason Thorpe wrote:
} Subject: Re: Things not referenced in kernel configs, but mentioned in fil
} > On Nov 12, 2018, at 11:12 AM, John Nemeth wrote:
} >
} > wbsio and wt also seems to fit in that category.
}
} Isn't "wt" an ancient PC tape drive? We should make an
> On Nov 12, 2018, at 11:12 AM, John Nemeth wrote:
>
> wbsio and wt also seems to fit in that category.
Isn't "wt" an ancient PC tape drive? We should make an effort to prune more
deadwood drivers.
-- thorpej
On Nov 12, 3:38pm, co...@sdf.org wrote:
} On Mon, Nov 12, 2018 at 10:23:26AM -0500, Greg Troxel wrote:
} > co...@sdf.org writes:
} >
} > > This is an automatically generated list with some hand touchups, feel
} > > free to do whatever with it. I only generated the output.
} > >
} > > ac100ic
} >
co...@sdf.org wrote:
>This is an automatically generated list with some hand touchups, feel
>free to do whatever with it. I only generated the output.
Maybe we could put your list somewhere under src/doc, src/doc/ORPHANS ?
Then delete lines as we add them to one or other of the ALL configs.
Hello,
On Mon, 12 Nov 2018 01:45:58 +
co...@sdf.org wrote:
> This is an automatically generated list with some hand touchups, feel
> free to do whatever with it. I only generated the output.
A good chunk of them are probably work in (various stages of) progress.
Like ...
> vac
... which
In article ,
Greg Troxel wrote:
>
>co...@sdf.org writes:
>
>> This is an automatically generated list with some hand touchups, feel
>> free to do whatever with it. I only generated the output.
>>
>> ac100ic
>> acemidi
>> acpipmtr
>> [snip]
>
>I wonder if these are candidates to add to an ALL
co...@sdf.org writes:
> So, I am excluding things that appear in ALL, and I am not checking if
But ALL is an x86 thing, currently.
> they appear as modules.
Interesting, but I suppose they then belong in ALL also.
> So far I had complaints about the appearance of 'lm' which cannot be
>
On Mon, Nov 12, 2018 at 10:23:26AM -0500, Greg Troxel wrote:
>
> co...@sdf.org writes:
>
> > This is an automatically generated list with some hand touchups, feel
> > free to do whatever with it. I only generated the output.
> >
> > ac100ic
> > acemidi
> > acpipmtr
> > [snip]
>
> I wonder if
co...@sdf.org writes:
> This is an automatically generated list with some hand touchups, feel
> free to do whatever with it. I only generated the output.
>
> ac100ic
> acemidi
> acpipmtr
> [snip]
I wonder if these are candidates to add to an ALL kernel, and if it will
turn out that they are
20 matches
Mail list logo
