From: "arun4linux" <arun4linux@indiatimes.com>
To: "Harlan Jillson" <Harlan.Jillson@pathfinderlwd.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: RH 8.0 vs. RH7.3 driver issues
Date: Thu, 12 Dec 2002 22:50:32 +0530 [thread overview]
Message-ID: <200212121725.WAA28045@WS0005.indiatimes.com> (raw)
HZ value for i686 has been modified from 100 to 512 in RH 8.0.
If you use this HZ value directly in your driver and , it could be a problem.
Warm Regards
Arun
"Harlan Jillson" wrote:
hi all,
I just subscribed to the list, and am looking for some suggestions.
I have a device driver for a RS485 card that does microlan
communications between several devices. The driver was written a couple
of years ago using the 2.2 kernel in RH 6.1. It's was updated for 2.4
kernel when RH7.3 was released and has been working fine. RH8.0 is
apparently a different story, as there appears to be problems with
scheduled timeouts (polling intervals) and maybe some interrupt issues.
My question is are there any known problems ( RH kernel 2.4.18-3)? I
know I'm dealing the revamps in the scheduler and timer areas and then
there's the shift from gcc 2.96 to 3.2.
Thanks for any suggestions,
Harlan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Get Your Private, Free E-mail from Indiatimes at http://email.indiatimes.com
Buy the best in Movies at http://www.videos.indiatimes.com
Change the way you talk. Indiatimes presents Valufon, Your PC to Phone service with clear voice at rates far less than the normal ISD rates. Go to http://www.valufon.indiatimes.com. Choose your plan. BUY NOW.
next reply other threads:[~2002-12-12 17:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-12 17:20 arun4linux [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-12 15:12 Harlan Jillson
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=200212121725.WAA28045@WS0005.indiatimes.com \
--to=arun4linux@indiatimes.com \
--cc=Harlan.Jillson@pathfinderlwd.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®