Re: [PARPORT] parport irq handler v7 test w/ 3 pp devices


David Campbell (campbell@torque.net)
Mon, 21 Sep 1998 16:17:20 +0800


*snip*

> The result in one sentence: No warnings, no data loss.

Horray!!
 
*snip*

> 2. As I said before the PHd is a very slow device and using it makes
> my Linux box slow as well. Even changing VCs are slow.
> I use the pd driver always with nice=1. I tried some cluster setting
> as well such as the default (64), 32, 16, 1. My machine's responsiveness
> weren't better. What can I do to achieve what I want? Maybe put some
> schedule(); in the pd driver? Where? Grant, can you suggest some points?
> :)

I will stay out of this one... All I can say is that schedule() in the wrong spot
can cause a kernel panic (if called from within any interrupt, software [polling]
or hardware).

David Campbell
=======================================================
campbell@torque.net

Current project list:
a) Maintain Linux ZIP drivers
b) Create Linux chipset specific parport drivers
c) Start on ParSCSI drivers
d) Boot proms for parport devices (socket onto NE2000 cards)

Any assistance to clearing this list most welcome

-- To unsubscribe, send mail to: linux-parport-request@torque.net --
-- with the single word "unsubscribe" in the body of the message. --



This archive was generated by hypermail 2.0b3 on Wed 30 Dec 1998 - 10:18:20 EST