[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Libcdio-devel] problems with libcdio on openbsd (and probably netbs
From: |
Edd Barrett |
Subject: |
Re: [Libcdio-devel] problems with libcdio on openbsd (and probably netbsd too) |
Date: |
Tue, 19 Jun 2018 22:24:44 +0100 |
User-agent: |
Mutt/1.10.0 (2018-05-17) |
Hi all,
A quick status update on the OpenBSD work.
On Mon, May 28, 2018 at 11:45:07AM +0100, Edd Barrett wrote:
> On Sun, May 27, 2018 at 02:22:48PM +0200, Robert Kausch wrote:
> > RAW_PART is always 2, thus 'c', in OpenBSD, but it's architecture dependent,
> > 2 or 3, in NetBSD [1]. So it would be a good idea to use RAW_PART instead of
> > a fixed 'c' or 'd' when looking for devices.
I had some time to work on libcdio tonight. I've made a git fork with a
branch off of your 2.0.0 tag (that's the version I'm targeting for now):
https://github.com/vext01/libcdio/commits/openbsd-porting
I'm having issues with cdda-player sadly, which suggests my work here is
not yet done. Can someone on Linux confirm if `cdda-player -s` works (to
stop playback).
I'm also seeing a whole load of this in the dmesg buffer:
Jun 19 22:15:43 arrakis /bsd: cd1(umass0:1:0): Check Condition (error 0x70) on
opcode 0x1a
Jun 19 22:15:43 arrakis /bsd: SENSE KEY: Illegal Request
Jun 19 22:15:43 arrakis /bsd: ASC/ASCQ: Invalid Command Operation Code
I've not yet had time to look into that one.
Thanks.
--
Best Regards
Edd Barrett
http://www.theunixzoo.co.uk
- Re: [Libcdio-devel] problems with libcdio on openbsd (and probably netbsd too),
Edd Barrett <=