From: "Ante Karamatić" <ivoks@grad.hr>
To: drbd-dev@lists.linbit.com
Subject: [Drbd-dev] Compatibility with 2.6.30 and current git
Date: Fri, 19 Jun 2009 16:39:11 +0200 [thread overview]
Message-ID: <4A3BA30F.70406@grad.hr> (raw)
Hi
I've mentioned this during Ubuntu 8.10 time frame, but nothing much has
changed since then.
Looking at linux/drbd.h, there's this part:
#ifndef CN_IDX_DRBD
# define CN_IDX_DRBD 0x4
/* Ubuntu "intrepid ibex" release defined CN_IDX_DRBD as 0x6 */
#endif
Ubuntu defined CN_IDX_DRBD as 0x6 cause 0x4 was taken by vesa
framebuffer device. Linux kernels 2.6.30 and latest git has both 0x4 and
0x6 taken by other modules (include/linux/connector.h):
#define CN_IDX_V86D 0x4
#define CN_DST_IDX 0x6
These IDs should be unique (hence the name 'Process Events connector
unique ids'). If you want 2.6.30 compatibility (at least), change it to
0x7. That one is free. But keep an eye on it for 2.6.31. So, something
like this:
#ifndef CN_IDX_DRBD
# define CN_IDX_DRBD 0x7
#endif
In current state, if vesa frame buffer module is loaded, drbd won't
work. Module will load, but userspace tools won't be able to connect to
it - they'll be connecting to frame buffer :)
Take care...
next reply other threads:[~2009-06-19 15:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 14:39 Ante Karamatić [this message]
2009-06-19 16:01 ` [Drbd-dev] Compatibility with 2.6.30 and current git Lars Ellenberg
2009-06-19 16:04 ` Ante Karamatić
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=4A3BA30F.70406@grad.hr \
--to=ivoks@grad.hr \
--cc=drbd-dev@lists.linbit.com \
/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.