Proposal for the new driver structure for Nextor v3 - please comment!

By konamiman

Paragon (1083)

konamiman's picture

07-08-2020, 09:31

Hi all. I announced this as a post in the Nextor v3 plans topic but maybe it deserves its own topic for visibility.

I have published a proposal for the new driver structure as a Gist in GitHub: https://gist.github.com/Konamiman/d9231c9f1e9f00a300c4e16647.... There are two files: one is an .asm file with the full driver structure, all methods fully commented; and the other one is a step by step guide on how to convert a v2 driver to a v3 guide.

Please take a look and comment as appropriate in the gist itself. I hope that the new structure is a good clarification/simplification over v2, while being detailed and extensible enough to cover any present and future need for drivers.

Login or register to post comments

By Grauw

Ascended (9272)

Grauw's picture

07-08-2020, 11:48

"It should have the fixed value "Nextor v3 driver","

I would (in general) omit the v and just have "Nextor 3 driver".

By sdsnatcher73

Paragon (1089)

sdsnatcher73's picture

07-08-2020, 12:43

I wonder what this string will be used for? Will the Nextor kernel read it, verify it? Will it be used to check compatibility? If so then we could use “Nextor 3.0 driver”, future (even minor versions) could then be identified and backwards compatibility could be implemented (certain functions may not work on 3.0 driver that do work on 3.1 but you could still use 3.1 kernel).

By konamiman

Paragon (1083)

konamiman's picture

07-08-2020, 14:27

This string will not be used for anything (there's a flag that tells it's a Nextor 3 driver already), but it needs to contain something in case some old tool reads it. Same for the old get version routine that now returns 0.0.0 and the deprecated functions that now just return an error.