This was added to GENERIC:
sel* at acpi?
and these four lines were added to files.acpi:
# SEL embedded controller
device sel
attach sel at acpi with sel_acpi
file dev/acpi/sel_acpi.c sel_acpi
With SEL0002 being the first item in the array, shouldn't it at least
match it if it exists? We will
On Tue, May 03, 2016 at 03:32:34PM -0500, Chase Davis wrote:
> Mike,
>
> We took your suggestion and re-wrote the driver to model sdhc_acpi. I
> have attached the new code. However, the match function never returns
> a 1. We put temporary print statements in the match routine. It is
> being
Mike,
We took your suggestion and re-wrote the driver to model sdhc_acpi. I
have attached the new code. However, the match function never returns
a 1. We put temporary print statements in the match routine. It is
being called several times during the kernel boot process, but it
never finds a
On Thu, Apr 28, 2016 at 02:18:25PM +0100, Stuart Henderson wrote:
> On 2016/04/28 08:56, stan wrote:
> > On Thu, Apr 28, 2016 at 08:44:49AM +0100, Stuart Henderson wrote:
> > > Stan, can you send the information that is output when you run
> > > sendbug -P as root? Just putting the whole thing
On Thu, Apr 28, 2016 at 03:22:15PM +, Stuart Henderson wrote:
> On 2016-04-28, stan wrote:
> > On Thu, Apr 28, 2016 at 02:18:25PM +0100, Stuart Henderson wrote:
> >> On 2016/04/28 08:56, stan wrote:
> >> > On Thu, Apr 28, 2016 at 08:44:49AM +0100, Stuart Henderson wrote:
> >>
On 2016-04-28, stan wrote:
> On Thu, Apr 28, 2016 at 02:18:25PM +0100, Stuart Henderson wrote:
>> On 2016/04/28 08:56, stan wrote:
>> > On Thu, Apr 28, 2016 at 08:44:49AM +0100, Stuart Henderson wrote:
>> > > Stan, can you send the information that is output when you run
>> > >
On Thu, Apr 28, 2016 at 02:18:25PM +0100, Stuart Henderson wrote:
> On 2016/04/28 08:56, stan wrote:
> > On Thu, Apr 28, 2016 at 08:44:49AM +0100, Stuart Henderson wrote:
> > > Stan, can you send the information that is output when you run
> > > sendbug -P as root? Just putting the whole thing
On Thu, Apr 28, 2016 at 08:44:49AM +0100, Stuart Henderson wrote:
> Stan, can you send the information that is output when you run
> sendbug -P as root? Just putting the whole thing inline in a
> reply-to-all to this mail would be fine. Please add "sysctl hw"
> output as well. Ideally we want a
On 2016/04/28 08:56, stan wrote:
> On Thu, Apr 28, 2016 at 08:44:49AM +0100, Stuart Henderson wrote:
> > Stan, can you send the information that is output when you run
> > sendbug -P as root? Just putting the whole thing inline in a
> > reply-to-all to this mail would be fine. Please add "sysctl
On Thu, Apr 28, 2016 at 08:44:49AM +0100, Stuart Henderson wrote:
> Stan, can you send the information that is output when you run
> sendbug -P as root? Just putting the whole thing inline in a
> reply-to-all to this mail would be fine. Please add "sysctl hw"
> output as well. Ideally we want a
Stan, can you send the information that is output when you run
sendbug -P as root? Just putting the whole thing inline in a
reply-to-all to this mail would be fine. Please add "sysctl hw"
output as well. Ideally we want a way to identify the watchdog
itself rather than the general machine type
On 2016-04-26, Theo de Raadt wrote:
>> int
>> selwd_probe(struct device *parent, void *match, void *aux)
>> {
>> struct isa_attach_args *ia = aux;
>> bus_space_tag_t iot;
>> bus_space_handle_t ioh;
>>
>> /* Match by device ID */
>> iot =
- Forwarded message from stan -
From: stan
To: Theo de Raadt
Subject: Re: watchdog suport for new hardware
Date: Tue, 26 Apr 2016 09:19:20 -0400
User-Agent: Mutt/1.5.4i
X-Operating-System: Debian GNU/Linux
X-Kernel-Version:
> int
> selwd_probe(struct device *parent, void *match, void *aux)
> {
> struct isa_attach_args *ia = aux;
> bus_space_tag_t iot;
> bus_space_handle_t ioh;
>
> /* Match by device ID */
> iot = ia->ia_iot;
> if (bus_space_map(iot, ia->ipa_io[0].base,
14 matches
Mail list logo