On Tue, Apr 26, 2016 at 06:44:34AM -0600, Theo de Raadt wrote:
> obviously you show the code, and then when the complexity/simplicity of it
> is seen, some people can jump in and help.
>
> that is the traditional way: show it
>
> >
> > --
> > A: Because it messes up the order in which people no
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 add
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 called
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 devic
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 inli
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:
> >> > > Stan, can you
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
>> > > sendbug -P as root?
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 inli
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 way
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 hw
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 way
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 etc.
Davis
>
> From: stan
> To: Stuart Henderson
> Subject: Re: FW: Re: watchdog suport for new hardware
> Date: Tue, 26 Apr 2016 11:57:48 -0400
> User-Agent: Mutt/1.5.4i
> X-Operating-System: Debian GNU/Linux
> X-Kernel-Version: 2.4.23
> X-Uptime: 11:51:45 up 91 days, 10
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 = ia->ia_iot;
>> if (bus_space_
- 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: 2.4.23
X-Uptime: 09:17:17 up 91 days, 8:18, 1 user, load
> 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, SELWD_IOSIZE
obviously you show the code, and then when the complexity/simplicity of it
is seen, some people can jump in and help.
that is the traditional way: show it
> We are embarking on a project where we will be using a number of
> industrially hardened computers manufactured by Schweitzer Engineering
>
We are embarking on a project where we will be using a number of
industrially hardened computers manufactured by Schweitzer Engineering
Laboratories, Inc. (SEL). SEL provides a very well whiten document
describing certain special features of these computers. One of these is a
hardware watchdog.
18 matches
Mail list logo
