sci-libs/andor-camera-driver-3.7.30008.0 fails to compile with sys-kernel/linux-headers-3.4 due to deprecated use of create_proc_read_entry and VM_RESERVED.

[omsai]

1. proc_fs removed create_proc_read_entry and instead suggest using proc_create[_data].
2. sysctl suggests using combinations of VM_IO, VM_DONTEXPAND, VM_HUGETLB, and VM_PFNMAP to replace VM_RESERVED http://article.gmane.org/gmane.linux.kernel.mm/83212/

Andor's bundled version of the BitFlow kernel driver often lags behind upstream, but BitFlow does not publically list their Linux SDK. Therefore BitFlow has been contracted to see if patches are available.

-*- mode: compilation; default-directory: "/usr/local/portage/sci-libs/andor-camera-driver/" -*-
Compilation started at Sun Feb 23 10:56:58

ebuild andor-camera-driver-3.7.30008.0.ebuild install
 * andor-sdk3-3.7.30008.0.tgz SHA256 SHA512 WHIRLPOOL size ;-) ...                                           [ ok ]
 * checking ebuild checksums ;-) ...                                                                         [ ok ]
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found kernel object directory:
 *     /lib/modules/3.10.7-gentoo/build
 * Found sources for kernel version:
 *     3.10.7-gentoo
 * Checking for suitable kernel configuration options...
 [ ok ]
>>> Unpacking source...
>>> Unpacking andor-sdk3-3.7.30008.0.tgz to /var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work
>>> Source unpacked in /var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work
>>> Preparing source in /var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor ...
/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv /var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor
/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor ...
 * Preparing bitflow module
make -j3 HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- 'LDFLAGS=-m elf_x86_64' -C /lib64/modules/3.10.7-gentoo/build M=/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv/ 
make: Entering directory `/usr/src/linux-3.10.7-gentoo'
  LD      /var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv//built-in.o
  CC [M]  /var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv//bflki.o
/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv//bflki.c: In function ‘bflki_publish’:
/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv//bflki.c:204:2: error: implicit declaration of function ‘create_proc_read_entry’ [-Werror=implicit-function-declaration]
/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv//bflki.c: At top level:
/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv//bflki.c:1252:2: error: ‘VM_RESERVED’ undeclared here (not in a function)
cc1: some warnings being treated as errors
make[1]: *** [/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv//bflki.o] Error 1
make: *** [_module_/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv/] Error 2
make: Leaving directory `/usr/src/linux-3.10.7-gentoo'
 * ERROR: sci-libs/andor-camera-driver-3.7.30008.0 failed (compile phase):
 *   emake failed
 * 
 * If you need support, post the output of `emerge --info '=sci-libs/andor-camera-driver-3.7.30008.0'`,
 * the complete build log and the output of `emerge -pqv '=sci-libs/andor-camera-driver-3.7.30008.0'`.
 * This ebuild is from an overlay named 'local': '/usr/local/portage/'
 * The complete build log is located at '/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/temp/environment'.
 * Working directory: '/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv'
 * S: '/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor'

Compilation exited abnormally with code 1 at Sun Feb 23 10:57:07

[erikhvatum]

FYI, I replaced vm_reserved with vm_dontexpand | vm_dontdump in order to build on 3.9 here, without side effects.

One thing to note: according to Norman with Andor 3rd party support, sdk3 does not support events, for example buffer overflow and exposure. I think he's referring to feature events, and the lack of support is observable in that, at least in my testing, any feature event callback is called immediately upon registration.

On Feb 23, 2014, at 10:42 AM, Pariksheet Nanda notifications@github.com wrote:

proc_fs removed create_proc_read_entry and instead suggest using proc_create[_data].

sysctl suggests using combinations of VM_IO, VM_DONTEXPAND, VM_HUGETLB, and VM_PFNMAP to replace VM_RESERVED http://article.gmane.org/gmane.linux.kernel.mm/83212/

Andor's bundled version of the BitFlow kernel driver often lags behind upstream, but BitFlow does not publically list their Linux SDK. Therefore BitFlow has been contracted to see if patches are available.

-- mode: compilation; default-directory: "/usr/local/portage/sci-libs/andor-camera-driver/" --
Compilation started at Sun Feb 23 10:56:58

ebuild andor-camera-driver-3.7.30008.0.ebuild install

• andor-sdk3-3.7.30008.0.tgz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ]
• checking ebuild checksums ;-) ... [ ok ]
• Determining the location of the kernel source code
• Found kernel source directory:

• /usr/src/linux
  

• Found kernel object directory:

• /lib/modules/3.10.7-gentoo/build
  

• Found sources for kernel version:

• 3.10.7-gentoo
  

• Checking for suitable kernel configuration options...
  [ ok ]

  Unpacking source...
  Unpacking andor-sdk3-3.7.30008.0.tgz to /var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work
  Source unpacked in /var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work
  Preparing source in /var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor ...
  /var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv /var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor
  /var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor
  Source prepared.
  Configuring source in /var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor ...
  Source configured.
  Compiling source in /var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor ...

• Preparing bitflow module
  make -j3 HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- 'LDFLAGS=-m elf_x86_64' -C /lib64/modules/3.10.7-gentoo/build M=/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv/
  make: Entering directory /usr/src/linux-3.10.7-gentoo' LD /var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv//built-in.o CC [M] /var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv//bflki.o /var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv//bflki.c: In function ‘bflki_publish’: /var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv//bflki.c:204:2: error: implicit declaration of function ‘create_proc_read_entry’ [-Werror=implicit-function-declaration] /var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv//bflki.c: At top level: /var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv//bflki.c:1252:2: error: ‘VM_RESERVED’ undeclared here (not in a function) cc1: some warnings being treated as errors make[1]: *** [/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv//bflki.o] Error 1 make: *** [_module_/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv/] Error 2 make: Leaving directory/usr/src/linux-3.10.7-gentoo'
• ERROR: sci-libs/andor-camera-driver-3.7.30008.0 failed (compile phase):
• emake failed
• If you need support, post the output of emerge --info '=sci-libs/andor-camera-driver-3.7.30008.0',
• the complete build log and the output of emerge -pqv '=sci-libs/andor-camera-driver-3.7.30008.0'.
• This ebuild is from an overlay named 'local': '/usr/local/portage/'
• The complete build log is located at '/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/temp/build.log'.
• The ebuild environment file is located at '/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/temp/environment'.
• Working directory: '/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv'
• S: '/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor'

Compilation exited abnormally with code 1 at Sun Feb 23 10:57:07
—
Reply to this email directly or view it on GitHub.

[omsai]

Thanks!

I've applied your vm_reserved fix and eselect'ed my previous 3.8 kernel
to workaround the deprecated create_prof_read_entry(). I pushed the
skeleton SDK3 ebuild, though I still haven't done any hardware testing
yet. I'll have a little time today evening and then the coming weekend
when I return from travels.

On 02/23/2014 10:28 PM, erikhvatum wrote:

FYI, I replaced vm_reserved with vm_dontexpand | vm_dontdump in order to
build on 3.9 here, without side effects.

One thing to note: according to Norman with Andor 3rd party support,
sdk3 does not support events, for example buffer overflow and exposure.
I think he's referring to feature events, and the lack of support is
observable in that, at least in my testing, any feature event callback
is called immediately upon registration.

On Feb 23, 2014, at 10:42 AM, Pariksheet Nanda
notifications@github.com wrote:

proc_fs removed create_proc_read_entry and instead suggest using
proc_create[_data].

sysctl suggests using combinations of VM_IO, VM_DONTEXPAND,
VM_HUGETLB, and VM_PFNMAP to replace VM_RESERVED
http://article.gmane.org/gmane.linux.kernel.mm/83212/

Andor's bundled version of the BitFlow kernel driver often lags behind
upstream, but BitFlow does not publically list their Linux SDK.
Therefore BitFlow has been contracted to see if patches are available.

-- mode: compilation; default-directory:
"/usr/local/portage/sci-libs/andor-camera-driver/" --
Compilation started at Sun Feb 23 10:56:58

ebuild andor-camera-driver-3.7.30008.0.ebuild install

• andor-sdk3-3.7.30008.0.tgz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ]
• checking ebuild checksums ;-) ... [ ok ]
• Determining the location of the kernel source code
• Found kernel source directory:
• /usr/src/linux
• Found kernel object directory:
• /lib/modules/3.10.7-gentoo/build
• Found sources for kernel version:
• 3.10.7-gentoo
• Checking for suitable kernel configuration options...
  [ ok ]

  Unpacking source...
  Unpacking andor-sdk3-3.7.30008.0.tgz to
  /var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work
  Source unpacked in
  /var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work
  Preparing source in
  /var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor ...

/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv
/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor
/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor

Source prepared.
Configuring source in
/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor ...
Source configured.
Compiling source in
/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor ...

• Preparing bitflow module
  make -j3 HOSTCC=x86_64-pc-linux-gnu-gcc
  CROSS_COMPILE=x86_64-pc-linux-gnu- 'LDFLAGS=-m elf_x86_64' -C
  /lib64/modules/3.10.7-gentoo/build
  M=/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv/

make: Entering directory `/usr/src/linux-3.10.7-gentoo'
LD
/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv//built-in.o

CC [M]
/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv//bflki.o

/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv//bflki.c:
In function ‘bflki_publish’:

/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv//bflki.c:204:2:
error: implicit declaration of function ‘create_proc_read_entry’
[-Werror=implicit-function-declaration]

/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv//bflki.c:
At top level:

/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv//bflki.c:1252:2:
error: ‘VM_RESERVED’ undeclared here (not in a function)
cc1: some warnings being treated as errors
make[1]: ***
[/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv//bflki.o]
Error 1
make: ***
[module/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv/]
Error 2
make: Leaving directory `/usr/src/linux-3.10.7-gentoo'

• ERROR: sci-libs/andor-camera-driver-3.7.30008.0 failed (compile phase):
• emake failed
  *
• If you need support, post the output of emerge --info '=sci-libs/andor-camera-driver-3.7.30008.0',
• the complete build log and the output of emerge -pqv '=sci-libs/andor-camera-driver-3.7.30008.0'.
• This ebuild is from an overlay named 'local': '/usr/local/portage/'
• The complete build log is located at
  '/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/temp/build.log'.
• The ebuild environment file is located at
  '/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/temp/environment'.
• Working directory:
  '/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv'
• S:
  '/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor'

Compilation exited abnormally with code 1 at Sun Feb 23 10:57:07
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
#23 (comment).

[erikhvatum]

I did some experimenting with feature events and looked carefully at
the SDK manual: feature events work correctly on Linux, but device
events, which are accessed through the EventSelector feature, do not
work.

Regarding feature events, the manual states, "As soon as this callback
is registered a single callback will be made immediately to allow the
callback handling code to perform any Initialisation code to set up
monitoring of the feature." I hadn't expected to be called back
immediately and misinterpreted that behavior as brokenness.

So, AndorSDK3 will notify you when a change to a feature that you
initiate modulates other features in turn, but the only notification
you can get from the SDK directly regarding exposure completion and
whatnot is that AT_WaitBuffer eventually returns after the exposure
has been transferred from the camera, through bitflow, through the
SDK, and into your buffer.

I am doing further experimentation to determine what impact this has
on maximum acquisition framerate. As an aside, if it does prove to be
a severe limitation, it may be possible to work around the lack of
events by interfacing the Linux box attached to the camera with the
camera's TTL port. This would provide exposure notifications and
allow the Linux box to trigger the camera in overlapped mode.

On Mon, Feb 24, 2014 at 5:29 AM, Pariksheet Nanda
notifications@github.com wrote:

Thanks!

I've applied your vm_reserved fix and eselect'ed my previous 3.8 kernel
to workaround the deprecated create_prof_read_entry(). I pushed the
skeleton SDK3 ebuild, though I still haven't done any hardware testing
yet. I'll have a little time today evening and then the coming weekend
when I return from travels.

On 02/23/2014 10:28 PM, erikhvatum wrote:

FYI, I replaced vm_reserved with vm_dontexpand | vm_dontdump in order to
build on 3.9 here, without side effects.

One thing to note: according to Norman with Andor 3rd party support,
sdk3 does not support events, for example buffer overflow and exposure.
I think he's referring to feature events, and the lack of support is
observable in that, at least in my testing, any feature event callback
is called immediately upon registration.

On Feb 23, 2014, at 10:42 AM, Pariksheet Nanda
notifications@github.com wrote:

proc_fs removed create_proc_read_entry and instead suggest using
proc_create[_data].

sysctl suggests using combinations of VM_IO, VM_DONTEXPAND,
VM_HUGETLB, and VM_PFNMAP to replace VM_RESERVED
http://article.gmane.org/gmane.linux.kernel.mm/83212/

Andor's bundled version of the BitFlow kernel driver often lags behind
upstream, but BitFlow does not publically list their Linux SDK.
Therefore BitFlow has been contracted to see if patches are available.

-- mode: compilation; default-directory:
"/usr/local/portage/sci-libs/andor-camera-driver/" --
Compilation started at Sun Feb 23 10:56:58

ebuild andor-camera-driver-3.7.30008.0.ebuild install

• andor-sdk3-3.7.30008.0.tgz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ]
• checking ebuild checksums ;-) ... [ ok ]
• Determining the location of the kernel source code
• Found kernel source directory:
• /usr/src/linux
• Found kernel object directory:
• /lib/modules/3.10.7-gentoo/build
• Found sources for kernel version:
• 3.10.7-gentoo
• Checking for suitable kernel configuration options...
  [ ok ]

  Unpacking source...
  Unpacking andor-sdk3-3.7.30008.0.tgz to
  /var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work
  Source unpacked in
  /var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work
  Preparing source in
  /var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor ...

/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv
/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor

/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor

Source prepared.
Configuring source in
/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor ...
Source configured.
Compiling source in
/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor ...

• Preparing bitflow module
  make -j3 HOSTCC=x86_64-pc-linux-gnu-gcc
  CROSS_COMPILE=x86_64-pc-linux-gnu- 'LDFLAGS=-m elf_x86_64' -C
  /lib64/modules/3.10.7-gentoo/build

M=/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv/

make: Entering directory `/usr/src/linux-3.10.7-gentoo'
LD

/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv//built-in.o

CC [M]

/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv//bflki.o

/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv//bflki.c:
In function 'bflki_publish':

/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv//bflki.c:204:2:
error: implicit declaration of function 'create_proc_read_entry'
[-Werror=implicit-function-declaration]

/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv//bflki.c:
At top level:

/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv//bflki.c:1252:2:
error: 'VM_RESERVED' undeclared here (not in a function)

cc1: some warnings being treated as errors
make[1]: ***

[/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv//bflki.o]
Error 1

make: ***

[module/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv/]
Error 2

make: Leaving directory `/usr/src/linux-3.10.7-gentoo'

• ERROR: sci-libs/andor-camera-driver-3.7.30008.0 failed (compile phase):
• emake failed
  *
• If you need support, post the output of emerge --info '=sci-libs/andor-camera-driver-3.7.30008.0',
• the complete build log and the output of emerge -pqv '=sci-libs/andor-camera-driver-3.7.30008.0'.
• This ebuild is from an overlay named 'local': '/usr/local/portage/'
• The complete build log is located at

'/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/temp/build.log'.

• The ebuild environment file is located at

'/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/temp/environment'.

• Working directory:

'/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor/bitflow/drv'

• S:
  '/var/tmp/portage/sci-libs/andor-camera-driver-3.7.30008.0/work/andor'

Compilation exited abnormally with code 1 at Sun Feb 23 10:57:07

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub

#23 (comment).

Reply to this email directly or view it on GitHub.

[matze]

Did you finally manage to compile the Bitflow driver on 3.1x kernels? I have a Neo which is basically unusable on any recent distributions.

[erikhvatum]

@matze looks like we are in luck: Andor posted an updated Linux SDK to MyAndor this morning. I downloaded it, and it builds against kernel 3.9.11 without modification, which is already an improvement over the old SDK. I'm about to head home for the weekend, so I'm reluctant to upgrade the kernel on our camera system at the moment :) I'll give it a try on Monday, however.

[matze]

Great news! I'll also try the new SDK on Monday.

[erikhvatum]

Crap... the new SDK still has bitflow code that is trying to use create_proc_read_entry, which doesn't exist is 3.10+.

I'm reading through the updated procfs docs and attempting to make the necessary changes to blkfi.c for 3.10+...

Update: the changes needed require more thought than I have time for at the moment. It's not just a matter of replacing the create_proc_read_entry call with create_proc_data, which allows associating a single void* user data blob. There is also an array of character arrays that comes from somewhere. Putting a lot of printks in there will help figure this out, but in any case requires running the driver where it works unmodified. So, I'm back on 3.9.11 with the latest SDK installed.

[matze]

I don't have Andor's approval yet but that's a pity :-/ Looking forward to your attempt.