Skip to contentSkip to conversation

driverfs is not for everything! (was: [PATCH] /proc/scsi/map )

DISCUSSION John Summerfield 2 participants 2 messages Jun 24, 2002 – Sep 4, 2002 2 messages not in the archive

Subsystems (2)
lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 4 lines

It's a matter of where to draw the line. Obviously when we're talking physical devices, my tcpip connection to www.yahoo.com is not one. My PS/2

I'm far from expert here, but isn't the network card important here?

Quoted 4 lines

If a device can be accessed by multiple machines concurrently, it should not be in driverfs.

Back in the 1970s I used a computer where disk drives, tape drives and RAM chould be physically connected to and used by more than one computer at once.

It was an IBM S/370 model 168 MP; you might argue the toss on the RAM, but the disk drives were beyond argument.

On which devices should MVS have ignored power cycling?

Signature · 10 lines
Cheers
John Summerfield

Microsoft's most solid OS: http://www.geocities.com/rcwoolley/

Note: mail delivered to me is deemed to be intended for me, for my disposition.

==============================
If you don't like being told you're wrong,
	be right!

A message that is not in the archive (sent off-list or not yet received): [email protected]

#3 lore raw

Re: Runlevel for Sleep?

Quoted 3 lines

I think we'll know better once we have working device power management if a new runlevel is needed or not.

I'll second this. It seems that everybody is spending time fiddling with workarounds instead of fixing the drivers.

Personally, I'm trying to get the e1000 driver to resume correctly. After resume, an ifconfig down, ifconfig up cycle works fine, so it can't be *that* hard. But my naive approach (run the down and up methods) doesn't do the trick, nor does merely running the close and open methods.

The analysis is complicated by the fact that the e1000 driver must be compiled as a module, and debugging modules with kgdb is a bit sketchy, and setting a breakpoint within the resume function always makes it segfault ... :(

-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390