Compatibility with 2.6.27
Hi
In 2.6.27, CN_IDX 0x4 is taken by v86d. Since this ID is used by drbd also, in some cases (when vesafb is loaded) drbd can't be loaded into kernel and vice versa.
This patch changes CN_IDX_DRBD to 0x6, which is free atm. This, of course, could change in future, and should be watched for. Other option would be to contact upstream and request an ID for drbd.
Take care
Signature · 2 lines
Ante Karamatić, [email protected] Ubuntu Server Team
From c18caf1c9596251c12c3de5e03a71c5ea804228a Mon Sep 17 00:00:00 2001
From: Ante Karamatic <[email protected]>
Date: Sat, 4 Oct 2008 20:22:46 +0200
Subject: [PATCH] Changed CN_IDX_DRBD to 0x6, since 0x4 is already occupied by v86d in
Linux kernel.
--- drbd/linux/drbd.h | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)
drbd/linux/drbd.h +1 -1
@@ -343,7 +343,7 @@ enum UuidIndex {/* The following line should be moved over to linux/connector.h * when the time comes */ -#define CN_IDX_DRBD 0x4 +#define CN_IDX_DRBD 0x6#define CN_VAL_DRBD 0x1struct drbd_nl_cfg_req {
Signature · 1 line
1.5.6.3
Lars Ellenberg
maintainerQuoted 5 lines · Ante Karamatic
Hi
In 2.6.27,
CN_IDX0x4is taken by v86d. Since this ID is used by drbd also, in some cases (when vesafb is loaded) drbd can't be loaded into kernel and vice versa.
thanks. we have known (and, unfortunately, ignored) that for a year now, V86D was added last October. guess we have to fix it now.
Lars