From: "Michael S. Zick" <mszick@morethan.org>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] [RFC]: rename ncr53c8xx to 53c720? [Was: D380 and ext[23] fs grave pb]
Date: Tue, 12 Sep 2006 07:26:22 -0500 [thread overview]
Message-ID: <200609120726.23020.mszick@morethan.org> (raw)
In-Reply-To: <200609120702.18615.mszick@morethan.org>
On Tue September 12 2006 07:02, Michael S. Zick wrote:
> On Tue September 12 2006 06:09, Joel Soete wrote:
> > Hello Matthew,
> >
> > May be now that parisc-linux tree is managed with git and that driver is
> > in fact only for ncr 53c720 hba, isn't it time to rename those stuff
> > like ncr53c8xx to 53c720?
> >
>
> Joel and group,
>
> I was browsing that code and noticed that it tries to support a half
> dozen different chips.
>
> That leads into some really strange looking code for the single-ended/
> differential setup.
>
Oops, sorry, getting old...
Noticed one more thing - the driver allocates kernel memory -
Which raised the question in my mind of:
*) Driver allocates memory
*) Memory request generates swap activity
*) Swap file is on same driver
Can the above sequence happen and deadlock the driver?
The "softlockup detected" in your message listing?
That driver also uses both spinlocks and timers, so
it may be affected by the recent changes.
Mike
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
prev parent reply other threads:[~2006-09-12 12:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <45018CEC.4040104@scarlet.be>
2006-09-11 13:29 ` [parisc-linux] w-a to what [Was: D380 and ext[23] fs grave pb] Michael S. Zick
2006-09-12 11:09 ` [parisc-linux] [RFC]: rename ncr53c8xx to 53c720? " Joel Soete
[not found] ` <200609120702.18615.mszick@morethan.org>
2006-09-12 12:26 ` Michael S. Zick [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=200609120726.23020.mszick@morethan.org \
--to=mszick@morethan.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox