dann frazier wrote:
On Thu, Dec 07, 2006 at 11:27:33AM -0500, Woody Suwalski wrote:
However, much better would be to create a symlink from /dev/temp to
/dev/temperature.
Reason: set_therm and fan_ctrl programs use /dev/temperature for setting the
thermostat configuration.
fand is taking advantage of 0.5 degree temperature resolution - using
propriatory ioctl call.
All of them need a non-standard /dev/temp interface. As such it should not be
attempted if the correct Netwinder driver is not installed.
Hence since it is hardware-specific, it may be better to keep it as a specific
/dev/ interface... (rename to nwtemp????)
So the quick fix will be to add /dev/temp to the man page. The proper - to add
/dev/temperature symlink to udev rules...
It sounds like you're saying that /dev/temp might, sometimes, not be
what I want to use. On a default etch install it has the same
major/minor as recommended in the manpage. So, by default it *is* what
I want to use.
Can you explain in more detail what the conditions are that would
cause /dev/temp to not be what I want? The only possibility I can see
is if there's another driver that I could load that would also use the
same major/minor but would provide an incompatible interface. In that
case I can understand why you might be using the device name to
differentiate, but that would only work if you're relying on a udev
environment that only exposes /dev entries if the right driver is
there. In other words, if /dev/temperature is there and the wrong
driver gets loaded, /dev/temperature will also be providing the wrong
interface.
If that's the case, it seems like the *right* answer is to make udev
create something like your suggested /dev/nwtemp with a unique
major/minor.
I don't see how a symlink is of any value - by doing a symlink we're
assuming /dev/temp is correct. But if its correct, why not use it
directly?
Physically you are correct.
However we really want to use /dev/temperature which is a SUPERSET of
Linux /dev/temp. We have not much use of /dev/temp without this extra
functionality.
I see it is rather for cross-incompability between architectures: there
is nothing wrong with trying to run Netwinder user-mode programs on any
other architecture, but I do not want to actually mess with _their_
/dev/temp, but get out if no propriatory /dev/temperature exists. Simply
on Netwinder with udev /dev/temp happens to provide this extra
functionality. BTW. You can run etch without udev, as I have
demonstrated up to today ;-)
So if "temperature" is not propriatory enough, it may need to be renamed
to nw_temperature or so. But this will break (maybe non-existant)
historical back-compatibility, so I would prefer to leave it...
As such - I disagree that symlink is of no value.... It has some logical
meaninig.
Martin, what is your expert opinion here?
Woody
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
