| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3704.1 | Requested more info | RDGENG::PRATTH | | Thu Jun 05 1997 04:26 | 7 |
|
I mailed Hans yesterday requesting more information on what sort of
device driver they are trying to port.
Helen.
|
| 3704.2 | Separate calls about the same/related issue.. | MUFFIT::helen | Helen Pratt | Thu Jun 05 1997 07:59 | 59 |
|
This call is getting a little confusing. Hans has logged 3 separate calls
over the last week all about the same/related problem and cross referencing
them. The point numbers are:
29440 - The base note.
29679 - This was handled by Galway.
30139 - A new one which I'll post here.
Hello,
In the book "Writing EISA and ISA Bus Device Drivers" number
AA-Q0R6C_TE, March 1996 Product Version Digital UNIX version 4.0 or
higher.
Chapter 2 EISA/ISA Bus Architectures, and 2.1 ISA Devices you read
following " To support the same device on the ISA bus, you MUST:
. Make sure the isa_option data table that resides in the
/usr/sys/data/isa_option_data.c file contains ....."
BUT when I open and read this file following warning text is
displayed before my eyes:
/*************************** Warning!!!************************************/
/**/
/* This table is not used to support device drivers in the 4.0 =
*/
/* release. It exists as a Notbinary entry in the alpha/files file =
*/
/* for the 4.0 release in order to support older device driver kits. */
/* It will be made Notbinary and remain in the kernel build in the =
*/
/* 5.0 release at the descression of the individual bus developers. =
*/
/*
*/
/*********************************************************************
*****/ WHAT MEANS????
As I mentioned in my query, no 29679, it is a problem for us to
dynamically configure my driver, you got the print outs from
"sysconfig" command earlier.
In the answer from you you talk about a customer writing this driver.
This answer I don't understand we are writing this driver our selves.
In the print out mentioned above one line content is that the
"/subsys/TMB16.mod" can't be found.
But reading the "Writing Device Drivers: Tutorial" No AA-PUBVD-TE
March 1996 Product Version: Digital UNIX Version 4.0 or higer nothing
is written that I should put anything in this directory. BUT reading
the "Programmer's Guide" No AA-PS30D-TE March 1996 Product Version:
Digital UNIX Version 4.0 or higher, Appendix C.5, It is written that
I should copy my module to the "/subsys" directory. Which book
should I follow or it is something else I can't follow here.
Please help me
Hans. ASAP No A70100.
|
| 3704.3 | Answer for 2nd part of 30139 | MUFFIT::helen | Helen Pratt | Thu Jun 05 1997 09:46 | 22 |
| I have sent the following to Hans with regard to the second part of his
second point:
>>But reading the "Writing Device Drivers: Tutorial" No AA-PUBVD-TE=20
>> March 1996 Product Version: Digital UNIX Version 4.0 or higer nothing=20
>> is written that I should put anything in this directory. BUT reading=20
>> the "Programmer's Guide" No AA-PS30D-TE March 1996 Product Version:=20
>> Digital UNIX Version 4.0 or higher, Appendix C.5, It is written that=20
>> I should copy my module to the "/subsys" directory. Which book=20
>> should I follow or it is something else I can't follow here.
You have two options:
1. Copy your module to the /subsys directory.
2. Create a soft link in the /subsys directory to your module.
This information is documented in sections on configuring a dynamic
device. For information on this refer to Section 14.3.1 "Step 1: Link
to the Single Binary Module" in the Writing Device Driver Tutorial.
Helen.
|
| 3704.4 | Reply from Hans | MUFFIT::helen | Helen Pratt | Fri Jun 06 1997 04:20 | 20 |
| I've recieved the following reply from Hans:
Hi Helen,
Sorry If I am too pedantic, but in the tutorial 14.3.1 Step 1 they
write "/var/subsys" and not "/subsys" that the "sysconfig" command
expected. I have of course already corrected my soft links so this was not
the main question in query 30139. It is the one you still are
investigating. My module is still not possible to install(configure)
dynamically into the kernel.
Query 29440 I probably still need your answer from. Perhaps my "work
around" is working but as long as I can't install the module I can't
test it. An example C-source module from an ISA driver should be most
welcome.
Yours gratefully,
Hans
|
| 3704.5 | Looking for sample isa driver | MUFFIT::helen | Helen Pratt | Fri Jun 06 1997 05:47 | 42 |
|
I've just sent the following to Hans:
Hi Hans,
Thanks for your mail.
There are two different ways to dynamically load device drivers in Digital
UNIX V4.0. The first involves adding an entry to the isa_option_data.c
file and the second involves adding a line to the /etc/sysconfigtab
file.
Adding an entry to the isa_option_data.c is the old method of doing this
and will not be supported in a future version of Digital UNIX - hence
the warning comment in the file.
Adding a entry to the /etc/sysconfigtab file for your device driver is
the recommended approach. A sample entry for an ISA device would
look something like the following (note that it all needs to be on
one continuous line):
ISA_Option = Board_Id - Null, Function_Name - 'KBD,MOUSE',
Driver_Name - gpc, Int_Aft_Attach - 1, Type - C, Adpt_Config - N
>> Query 29440 I probably still need your answer from. Perhaps my "work
>> around" is working but as long as I can't install the module I can't
>> test it. An example C-source module from an ISA driver should be most
>> welcome.
I'm still trying to track down an ISA driver sample...
Let me know how if the above helps,
regards,
Helen.
ps. If you continue to have problemswith the load, can you send me an
update of the output your get from sysconfig, when you attempt to load
the driver?
|