All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mischa Baars <mjbaars1977.linux-block@cyberfiber.eu>
To: Jens Axboe <axboe@kernel.dk>, linux-block@vger.kernel.org
Subject: Re: packet writing support
Date: Mon, 07 Oct 2019 16:19:38 +0200	[thread overview]
Message-ID: <c7a184d86cc64b649cbdcfc1542a30cf74f78624.camel@cyberfiber.eu> (raw)
In-Reply-To: <99b7b647-8788-8a20-e052-db3306837e2f@kernel.dk>

On Mon, 2019-10-07 at 08:10 -0600, Jens Axboe wrote:
> On 10/7/19 1:02 AM, Mischa Baars wrote:
> > > Let's keep this very simple:
> > > 
> > > 1) Have you used the pktcdvd code at all? How much?
> > 
> > Where are talking about the kernel/drivers/block/pktcdvd.ko.xz module.
> > I have not used it directly, as it is a kernel module. Instead I have
> > been working with K3b, the KDE cdwriting software package.
> 
> Let's keep it even simpler - why do you think you are using the pktcdvd
> code at all? If you're using k3b to burn CDs or DVDs, then you are not
> using that code at all. You'd have to actively setup a devie using
> pktsetup, and you'd then mount it with UDF to write files. Doesn't sound
> like what you are doing at all, which renders this whole discussion
> pointless.
> 

I would not dare call it pointless. I have here a k3b application that has proven to work in the past, yet now it does not show any willingness to cooperate.
Until recently, I was still able to read CD's / DVD's from the filemanager, but since I installed the linux-next kernel, the driver doesn't even show up using
'fdisk -l' (with SCSI cdrom support compiled in).


  reply	other threads:[~2019-10-07 14:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-05 10:12 packet writing support Mischa Baars
2019-10-05 15:50 ` Jens Axboe
2019-10-06  7:31   ` Mischa Baars
2019-10-06 15:10     ` Jens Axboe
2019-10-07  7:02       ` Mischa Baars
2019-10-07  7:23         ` Hannes Reinecke
2019-10-07  8:07           ` Mischa Baars
2019-10-07  8:45             ` Hannes Reinecke
2019-10-07  9:11               ` Mischa Baars
2019-10-07  9:17                 ` Mischa Baars
2019-10-07 14:22                   ` Bart Van Assche
2019-10-07 14:36                     ` Mischa Baars
2019-10-07 16:13                     ` Mischa Baars
2019-10-07 16:19                       ` Jens Axboe
2019-10-07 17:31                         ` Mischa Baars
2019-10-07 10:02                 ` Hannes Reinecke
2019-10-07 14:10         ` Jens Axboe
2019-10-07 14:19           ` Mischa Baars [this message]
2019-10-06  8:31   ` Mischa Baars
2019-10-06 20:48     ` Laurence Oberman
2019-10-07  8:10       ` Mischa Baars
2019-10-07  9:02       ` Mischa Baars
  -- strict thread matches above, loose matches on Subject: below --
2019-10-04  9:22 Mischa Baars
2019-10-04  9:21 Mischa Baars

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=c7a184d86cc64b649cbdcfc1542a30cf74f78624.camel@cyberfiber.eu \
    --to=mjbaars1977.linux-block@cyberfiber.eu \
    --cc=axboe@kernel.dk \
    --cc=linux-block@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 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.