public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Andres Salomon <dilinger@queued.net>
Cc: cbou@mail.ru, linux-kernel@vger.kernel.org, dwmw2@infradead.org
Subject: Re: [PATCH 4/4] power_supply: bump EC version check that we refuse to run with in olpc_battery
Date: Wed, 30 Apr 2008 14:55:15 -0700	[thread overview]
Message-ID: <20080430145515.bbee90d9.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080430163030.29e1ca9f@ephemeral>

On Wed, 30 Apr 2008 16:30:30 -0400
Andres Salomon <dilinger@queued.net> wrote:

> 
> Refuse to run with an EC < 0x44.  We're playing it safe, and this is
> a pretty old EC version.
> 
> Also, add a comment about why we're checking the EC version.

Sigh.  Presantly, the entirety of olpc_battery.c looks very nice
in an 80-column display.

> 
> diff --git a/drivers/power/olpc_battery.c b/drivers/power/olpc_battery.c
> index cb45a67..086b146 100644
> --- a/drivers/power/olpc_battery.c
> +++ b/drivers/power/olpc_battery.c
> @@ -398,7 +398,12 @@ static int __init olpc_bat_init(void)
>  
>  	if (!olpc_platform_info.ecver)
>  		return -ENXIO;
> -	if (olpc_platform_info.ecver < 0x43) {
> +
> +	/*
> +	 * We've seen a number of EC protocol changes; this driver requires
> +	 * the latest EC protocol, supported by 0x44 and above.
> +	 */
> +	if (olpc_platform_info.ecver < 0x44) {
>  		printk(KERN_NOTICE "OLPC EC version 0x%02x too old for battery driver.\n", olpc_platform_info.ecver);
>  		return -ENXIO;

Now it needs 0x80 :(

  reply	other threads:[~2008-04-30 21:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-30 20:30 [PATCH 4/4] power_supply: bump EC version check that we refuse to run with in olpc_battery Andres Salomon
2008-04-30 21:55 ` Andrew Morton [this message]
2008-04-30 23:12   ` Andres Salomon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080430145515.bbee90d9.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=cbou@mail.ru \
    --cc=dilinger@queued.net \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox