Re: (NEWBIE) Networking Problems
From: jpd (read_the_sig_at_do.not.spam.it)
Date: 04/14/04
- Next message: Frank da Cruz: "ANNOUNCE: C-Kermit 8.0.211"
- Previous message: glen herrmannsfeldt: "Re: (NEWBIE) Networking Problems"
- In reply to: glen herrmannsfeldt: "Re: (NEWBIE) Networking Problems"
- Next in thread: glen herrmannsfeldt: "Re: (NEWBIE) Networking Problems"
- Reply: glen herrmannsfeldt: "Re: (NEWBIE) Networking Problems"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 14 Apr 2004 05:39:21 +0000 (UTC)
On 2004-04-14, glen herrmannsfeldt <gah@ugcs.caltech.edu> wrote:
[snip]
>
> Couldn't it enable interrupts with interrupt vectors pointing
> to different places that would indicate which one it was, and
> then convince the card to interrupt, such as sending a packet
> and emptying the transmit buffer?
*crunch* *crunch* ehrm. Oh, I think I get what you want to do.
I still don't see the point in it, though. And usually you need
interrupts to efficiently *receive* packets, not transmit them.
But still, that doesn't help you with the case where you don't
know where the card is interrupting. You can't just send a packet
and hope somebody sends one back, monitoring all IRQs, then try
and correlate which one it is. Before you know it you'll end up
abusing the clock or keyboard or disk interrupt or so.
> Maybe drivers aren't allowed to do that during boot time, though.
At boot time you either have a preconfigured kernel or you tell the
kernel using the boot configurator where the apropriate irqs and
addresses are.
-- j p d (at) d s b (dot) t u d e l f t (dot) n l .
- Next message: Frank da Cruz: "ANNOUNCE: C-Kermit 8.0.211"
- Previous message: glen herrmannsfeldt: "Re: (NEWBIE) Networking Problems"
- In reply to: glen herrmannsfeldt: "Re: (NEWBIE) Networking Problems"
- Next in thread: glen herrmannsfeldt: "Re: (NEWBIE) Networking Problems"
- Reply: glen herrmannsfeldt: "Re: (NEWBIE) Networking Problems"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|