From: "Diego Elio Pettenò" <flameeyes@flameeyes.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cdrom: debug info changes, Beurer glucometer support
Date: Sun, 13 Oct 2019 14:38:46 +0100 [thread overview]
Message-ID: <CAHcsgXTM2ry--LDO=rMg54nYRF+YeVMeoCpig=fEAyrMDiLfcw@mail.gmail.com> (raw)
In-Reply-To: <20190826151640.5036-1-flameeyes@flameeyes.com>
On Mon, Aug 26, 2019 at 4:16 PM Diego Elio Pettenò
<flameeyes@flameeyes.com> wrote:
> I've been hacking around the cdrom driver so that I could get Linux to
> mount and access the virtual CD device used by the Beurer GL50 evo
> glucometer. The device is fairly quirky and goes into a reset cycle on a
> vanilla kernel.
Hi Jens, any chance you could take a look at these patches? I'm not
making much progress on figuring out the higher level protocol of the
meter, and it would be easier if I could connect it directly to my
machine, rather than having to jump through VMs :(
Thanks!
prev parent reply other threads:[~2019-10-13 13:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 15:16 cdrom: debug info changes, Beurer glucometer support Diego Elio Pettenò
2019-08-26 15:16 ` [PATCH 1/4] cdrom: remove entering/exiting debug message logs Diego Elio Pettenò
2019-08-26 15:16 ` [PATCH 2/4] cdrom: make debug logging rely on pr_debug and debugfs only Diego Elio Pettenò
2019-11-03 16:00 ` Michal Suchánek
2019-11-11 12:21 ` Diego Elio Pettenò
2019-11-11 13:18 ` Michal Suchánek
2019-11-11 13:27 ` Diego Elio Pettenò
2019-08-26 15:16 ` [PATCH 3/4] cdrom: remove REVISION/VERSION constants that are awfully out of date Diego Elio Pettenò
2019-08-26 15:16 ` [PATCH 4/4] cdrom: support Beurer GL50 evo CD-on-a-chip devices Diego Elio Pettenò
2019-10-13 13:38 ` Diego Elio Pettenò [this message]
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='CAHcsgXTM2ry--LDO=rMg54nYRF+YeVMeoCpig=fEAyrMDiLfcw@mail.gmail.com' \
--to=flameeyes@flameeyes.com \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).