On 21/05/07, Thomas De Schampheleire <[EMAIL PROTECTED]> wrote:
The exact location (/proc or elsewhere) is no point for me, but I do
find this mechanism an extremely useful feature.
You could try running mdb -wk and then patching globals in your module
from there.
Paul
--
Paul Durrant
http
Thomas De Schampheleire wrote:
On 5/21/07, Darren J Moffat <[EMAIL PROTECTED]> wrote:
Thomas De Schampheleire wrote:
> You're right that this probably is the cleanest solution.
>
> However, this does not work for anything other than a debug parameter
> right? Suppose I want to communicate with t
On 5/21/07, Darren J Moffat <[EMAIL PROTECTED]> wrote:
Thomas De Schampheleire wrote:
> You're right that this probably is the cleanest solution.
>
> However, this does not work for anything other than a debug parameter
> right? Suppose I want to communicate with the module, for something
> else.
Thomas De Schampheleire wrote:
You're right that this probably is the cleanest solution.
However, this does not work for anything other than a debug parameter
right? Suppose I want to communicate with the module, for something
else. How can I do this?
An ioctl on the drivers device node, eg:
You're right that this probably is the cleanest solution.
However, this does not work for anything other than a debug parameter
right? Suppose I want to communicate with the module, for something
else. How can I do this?
In Linux, drivers and modules can use the /proc filesystem to pass
informat
Thomas De Schampheleire wrote:
Basically, I would like to be able to pass a debug_level parameter to
my module, that determines the amount of messages that will pass on
the console. If there is another way to achieve this, that is fine for
me as well.
Rather than using console debugging it migh
Thomas De Schampheleire wrote:
Hi,
Device drivers can use functions like ddi_prop_get_int(xx_dev, xx_dip,
0, "width", XX_DEFAULT_WIDTH); to retrieve configurations from their
driver.conf file.
I am wondering whether a similar mechanism can be used for kernel
modules. I am not sure which values
Hi,
Device drivers can use functions like ddi_prop_get_int(xx_dev, xx_dip,
0, "width", XX_DEFAULT_WIDTH); to retrieve configurations from their
driver.conf file.
I am wondering whether a similar mechanism can be used for kernel
modules. I am not sure which values I would need to put in as dev_t
