From: "David L" <idht4n@hotmail.com>
To: arjanv@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: bad: scheduling while atomic!: how bad?
Date: Sat, 18 Jun 2005 16:19:58 -0700 [thread overview]
Message-ID: <BAY104-F295AF1E9F80CC64DDEF85784F70@phx.gbl> (raw)
In-Reply-To: <20050618225238.GB23688@devserv.devel.redhat.com>
> > >On Sat, 2005-06-18 at 14:59 -0700, David L wrote:
> > >> I'm seeing the message:
> > >>
> > >> bad: scheduling while atomic!
> > >>
> > >> I see this dozens of times when I'm writing to a nand flash device
>using
> > >a
> > >> vendor-provided driver from Compulab in 2.6.8.1. Does this mean the
> > >driver
> > >> has a bug or is incompatible with the preemptive configuration
>option?
> > >How
> > >> bad is "bad"? Should I turn of the preemption option, ignore the
> > >message,
> > >> or what?
> > >
> > >can you post the sourcecode of the driver? it needs fixing...
> > It's on-line at:
> >
> > http://www.compulab.co.il/686-developer.htm
> >
> > under "Linux - kernel, drivers and patches".
> >
> > After unzipping, it's in:
> >
> > Drivers & Patches 2.6/Flash Disk/cl_fdrv.tgz
>
>that's only part of the source though... can you point at the full one ?
I'm pretty sure that's all the source... there was some documentation that
told how to edit the drivers/block/Kconfig and Makefile to actually build
it... below are the instructions. With just what was in that directory, I
was able to use their driver.
Cheers...
David
Copy the file cl_fdrv.tar.gz into the directory <kernel_src>/drivers/block
Then run
cd <kernel_src>/drivers/block
tar xfz cl_fdrv.tar.gz
Then open the file <kernel_source>/drivers/block/Kconfig
and, after line menu "Block devices"
add 3 following lines
config 686CORE_FLASH
tristate "686CORE flash drivers"
source "drivers/block/cl_fdrv/Kconfig"
and save the file.
Then open the file
<kernel_source>/drivers/block/Makefile
and, after line
obj-y := elevator.o ll_rw_blk.o ioctl.o genhd.o scsi_ioctl.o
add 3 following lines
# ifdef CONFIG_686CORE_FLASH
obj-y += cl_fdrv/
# endif
and save the file.
Run make gconfig (or any other configuration option) and the selection of
the flash driver will be available at Device Drivers >> Block Devices.
Run make bzImage from the directory <kernel_source> to finish building the
kernel.
_________________________________________________________________
Dont just search. Find. Check out the new MSN Search!
http://search.msn.click-url.com/go/onm00200636ave/direct/01/
next prev parent reply other threads:[~2005-06-18 23:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-18 21:59 David L
2005-06-18 22:10 ` Arjan van de Ven
2005-06-18 22:49 ` David L
2005-06-18 22:52 ` Arjan van de Ven
2005-06-18 23:19 ` David L [this message]
2005-06-18 23:46 ` Arjan van de Ven
2005-06-18 22:18 ` Lee Revell
2005-06-18 22:33 ` David L
2005-06-19 0:50 ` Lee Revell
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=BAY104-F295AF1E9F80CC64DDEF85784F70@phx.gbl \
--to=idht4n@hotmail.com \
--cc=arjanv@redhat.com \
--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
all inboxes | Powered by JetHome®