| Re: [hatari-devel] Re: Hatari SCSI Driver patch |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] Re: Hatari SCSI Driver patch
- From: Uwe Seimet <Uwe.Seimet@xxxxxxxxx>
- Date: Wed, 28 Oct 2015 23:35:52 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1446071753; l=1251; s=domk; d=seimet.de; h=In-Reply-To:Content-Transfer-Encoding:Content-Disposition: Content-Type:MIME-Version:References:Subject:To:From:Date; bh=/jUdpRR+6dNScctZxd6CyP2EQ0X9nFTYrY4saJVhw6g=; b=u+OQ1amfZr7tq2KziPLwYBqQ2FDxsHkNu6GkKS620ENQXqYmdh9hK2NpqkSf2e9Rl3n jo13gZSpU8P76l+VJg44lQZ4WRnlFhjUgrG4aEa/JgOFLW89HxVwqhgNsYIUwD5SVzqyC XjoXRY2B7KnqFk/+u9/iMe54AUkHk6AIV+A=
Hi,
Just to make things more transparent: If udev is not running, media
changes will be directly detected by the Atari application using the
SCSI Driver, based on the SCSI error code returned when accessing a
device. But if udev is running, udev detects the media change and the
Atari application will never see the SCSI error code. This is why
special treatment is required on systems running udev, and that's what
the udev-related code is for.
If libudev is present (headers and library) but not running Hatari will
still be linked against it, but for the SCSI Driver udev not running is
effectively the same as udev not being available at all.
Take care
Uwe
> Hi,
>
> keskiviikko 28 lokakuu 2015 23:10:13 Nicolas Pomarède kirjoitti:
> > Le 28/10/2015 08:39, Uwe Seimet a écrit :
> > > Should be better now, please see attachment.
> >
> > just a small note : since you define HAVE_UDEV to check if udev is
> > available, I think you could remove the "#if defined(__linux__)" (in
> > reset.c for example) and keep only the HAVE_xxxx coming from cmake
>
> Linux check is for enabling the whole driver.
>
> HAVE_UDEV is just for enabling additional media detection support
> in the driver.
>
>
> - Eero
>
>
>