From: Joseph Garcia <jpgarcia@execpc.com>
To: "linuxppc-dev@lists.linuxppc.org" <linuxppc-dev@lists.linuxppc.org>
Subject: bmac module broken
Date: Fri, 18 Feb 2000 08:01:13 -0600 [thread overview]
Message-ID: <38AD50A9.B95BEA7F@execpc.com> (raw)
With the recent mention of making dmasound a module to turn off sound when not
in use and save power, i wondered about the status of two other chips in the
pbg3. Specifically, the bmac, and the mesh. Bmac panics upon a second install,
so something is missing in the cleanup i guess. also, it doesn't power it off.
borrowing from the sleep code, adding the following lines before freeing
bmac_devs does turn it off. i dont know if i need the reset.
feature_set(bp->node, FEATURE_BMac_reset);
udelay(10000);
feature_clear(bp->node, FEATURE_BMac_IO_enable);
udelay(10000);
However, it still panics on a second install. this is similar to the problem
with dmasound a few months ago. I think i tried changing the free_irq's second
parameter to that of the last param in the corresponding request_irq, but it
didn't work for me. Ideas/patches?
Also, mesh would be a nice one to modulize. building the module, it complains
about kernel version. modversions are not enabled in this. i plan on a fix.
Also, there is no module_init or cleanup in it, but other scsi modules dont
either. But like the others, I'd want to be able to rmmod this just so it turns
off the chip, and later i can reinstall it without a panic. I'd think the
powerdown would have to go in the cleanup since the only calls to mesh_power are
in init(on only) and sleep. Any tips?
Any other chips that can/should be turned off? are media bays are off when not
in use? Pcmcia?
Thank you for your time.
--
Joseph P. Garcia jpgarcia@execpc.com jpgarcia@lidar.ssec.wisc.edu
CS Undergraduate Student Employee - Systems Programmer
University of Wisconsin - Madison UW Lidar Group
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2000-02-18 14:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=38AD50A9.B95BEA7F@execpc.com \
--to=jpgarcia@execpc.com \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).