public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: stepan@suse.de (Stefan Reinauer)
To: "Richard A. Smith" <rsmith@bitworks.com>
Cc: "linuxbios@lanl.gov" <linuxbios@lanl.gov>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: jedec_probe_chip error?
Date: Fri, 5 Apr 2002 20:54:03 +0200	[thread overview]
Message-ID: <20020405205403.A28921@suse.de> (raw)
In-Reply-To: <MDAEMON-F200204051113.AA130309MD40469@bitworks.com>; from rsmith@bitworks.com on Fri, Apr 05, 2002 at 11:09:54AM -0600

* Richard A. Smith <rsmith@bitworks.com> [020405 19:09]:
> >get /dev/bios from the OpenBIOS cvs tree:
> >http://www.freiburg.linux.de/OpenBIOS/dev/cvs.html
> 
> The Readme lists that this should work under a 2.2.x kernel, however
> I get serveral errors trying to compile with 2.2.19 
[..] 
> Does it sill work with 2.2.x?

Oops. I dropped 2.2 support with one of the last releases. It is tested
under 2.4 - backporting it shouldnt be too hard - drop me a note if 2.4 
is not an option for you.
 
> I'm using the latest tarball from the above link.  I was unable to
> get a CVS copy as it kept complaining that 'anonymous' was an unknown
> user.

Hmm... I'll check into that asap.

Best regards,
  Stefan Reinauer
  
-- 
Ok hex 4666 dup negate do i 4000 dup 2* negate do " *" 0 dup 2dup 1e 0 do
 2swap * e >>a 2* 5 pick + -rot - j + dup dup * e >>a rot dup dup * e >>a 
  rot swap 2dup + 10000 > if 3drop 3drop "  " 0 dup 2dup leave then loop 
              2drop 2drop type 268 +loop cr drop 5de +loop

      reply	other threads:[~2002-04-05 18:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-04  2:21 jedec_probe_chip error? Jeremy Jackson
2002-04-04  3:25 ` Eric W. Biederman
2002-04-04 10:36 ` Stefan Reinauer
2002-04-05 17:09   ` Richard A. Smith
2002-04-05 18:54     ` Stefan Reinauer [this message]

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=20020405205403.A28921@suse.de \
    --to=stepan@suse.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linuxbios@lanl.gov \
    --cc=rsmith@bitworks.com \
    /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