From: Johannes Meixner <jsmeix@suse.de>
To: Till Kamppeter <till.kamppeter@gmail.com>
Cc: abel deuring <adeuring@gmx.net>,
sebastien michea <sebastien.michea@manaty.net>,
sane-devel@alioth-lists.debian.net,
OpenPrinting <printing-architecture@lists.linux.dev>
Subject: Re: [sane-devel] OpenDeviceDB lists the scanners SANE supports, with links to the backend man pages
Date: Tue, 27 Oct 2026 08:59:24 +0100 [thread overview]
Message-ID: <ada980b7ba769e5244d02e63529f9333@suse.de> (raw)
In-Reply-To: <f3eda259-3182-4599-9954-5b6307feccd7@gmail.com>
Hello,
On 2026-10-26 17:59, Till Kamppeter wrote:
...
> I got asked the same but for OpenPrinting
> and printer drivers.
>
> I think, any device about which we know whether,
> how, and how well it works with Linux and
> open source in general should be listed by
> https://opendevicedb.org/.
>
> Windows users who want to switch to Linux ...
Currently
https://opendevicedb.org/
reads:
---------------------------------------------------
Before you reverse engineer a device,
check if someone already did.
An open directory of devices whose protocols
or firmware have been reverse engineered,
so nobody — human or AI agent — redoes work
that already exists.
---------------------------------------------------
and
https://opendevicedb.org/about/
provides a bit more info about the WHY.
As far as I understand that, the intent of
https://opendevicedb.org/
is not a complete list of devices which are supported
by whatever operating system for arbitrary end-users
but instead
for device driver software developers a list of
devices which do not support a published standard
so reverse engineering of protocol or firmware
is needed to make device driver software.
Kind regards
Johannes Meixner
--
SUSE Software Solutions Germany GmbH
Frankenstr. 146 - 90461 Nuernberg - Germany
GF: Stefan Gaiser, Jochen Jaser, Abhinav Puri
(HRB 36809, AG Nuernberg)
next prev parent reply other threads:[~2026-10-27 7:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAD_QBAQv8tgP5AWTAk_YzQ+YxihAukHjVrMyFFZpo3Q7M=iHdA@mail.gmail.com>
[not found] ` <dfa6ce9bc7761f0d7f30d21e8cff0b0e2075c8d5.camel@gmx.net>
2026-10-26 16:59 ` [sane-devel] OpenDeviceDB lists the scanners SANE supports, with links to the backend man pages Till Kamppeter
2026-10-26 20:38 ` abel deuring
2026-10-27 7:59 ` Johannes Meixner [this message]
2026-10-27 17:03 ` abel deuring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ada980b7ba769e5244d02e63529f9333@suse.de \
--to=jsmeix@suse.de \
--cc=adeuring@gmx.net \
--cc=printing-architecture@lists.linux.dev \
--cc=sane-devel@alioth-lists.debian.net \
--cc=sebastien.michea@manaty.net \
--cc=till.kamppeter@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.