All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Carlos O'Donell Jr." <carlos@megatonmonkey.net>
To: Albert Strasheim <fullung@ilink.nis.za>,
	parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Non-atomic __set_bit
Date: Sat, 29 Sep 2001 13:27:19 -0400	[thread overview]
Message-ID: <20010929132719.A15266@megatonmonkey.net> (raw)
In-Reply-To: <20010929020915.A24794@dogbert.localdomain>; from fullung@ilink.nis.za on Sat, Sep 29, 2001 at 02:09:15AM +0200

> Hello,
> 
> Is this going into CVS any time soon? It seems to work fine on my
> 720/50.
> 
> Regards,
> 
> Albert
> 

Albert,

Have you booted a devfs kernel on you box?
Does it seem to function properly?

Adding devfs to my kernel causes some odd stuff to go on after
trying to enter INIT. Though I haven't had time to sort it out.
The kernel boots fine, but probably one of the startup scripts
is doing something decidedly wrong.

Since you are using init=/bin/sh, and unless you tell devfs
to explicitly mount at boot, you won't _really_ be using 
devfs :)

Sure, it compiles... and it looks like it should work.
But theory and practice are so different it's not funny.

<Carlos looks back at the RF Amplifier design he has on the
whiteboard and chuckles>

c.

> 
> > parisc,
> > 
> > Walking the source for devfs and thinking about Alberts problem.
> > 
> > Would the non-working devfs be fixed by adding:
> > 
> > Non-atomic versions of set_bit e.g. __set_bit 
> > and test_and_set_bit e.g. __test_and_set_bit
> > to linux/include/asm-parisc/bitops.h?
> > 
> > I have the latest CVS linux module.
> > I've patched against that. It compiles now ;)
> > (god bless make -j8)
> > 
> > I'm currently sleepy, but I'll post the patch, and test
> > it tommorow on a 712/60 and 715/50.
> > 
> > c.
> 
> <patch snipped>

  reply	other threads:[~2001-09-29 17:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-24  6:10 [parisc-linux] Non-atomic __set_bit Carlos O'Donell Jr.
2001-09-29  0:09 ` Albert Strasheim
2001-09-29 17:27   ` Carlos O'Donell Jr. [this message]
2001-09-29 21:43     ` Albert Strasheim

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=20010929132719.A15266@megatonmonkey.net \
    --to=carlos@megatonmonkey.net \
    --cc=fullung@ilink.nis.za \
    --cc=parisc-linux@lists.parisc-linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.