Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Pacho Ramos <pacho@gentoo.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: bluez-5.0 dropped --with-ouifile=PATH
Date: Sun, 30 Dec 2012 10:43:03 -0800	[thread overview]
Message-ID: <1356892983.19248.82.camel@aeonflux> (raw)
In-Reply-To: <1356878136.18481.1.camel@belkin4>

Hi Pacho,

> That option is needed on Gentoo to let it catch oui.txt file present
> on /usr/share/misc/oui.txt, could it be re-added to prevent us from
> needing to sed src/oui.c looking for that file in our location?

or you build against a recent version of udev that comes with hwdb
support. Then it will actually start using the efficient version of
reading the OUI values from this file.

There is no plan to keep support for oui.txt for very long. It is still
supported as transition period, but that is about it.

Regards

Marcel



  reply	other threads:[~2012-12-30 18:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-30 14:35 bluez-5.0 dropped --with-ouifile=PATH Pacho Ramos
2012-12-30 18:43 ` Marcel Holtmann [this message]
2012-12-30 19:58   ` Pacho Ramos
2012-12-30 20:05     ` Marcel Holtmann
2012-12-30 20:12       ` Pacho Ramos

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=1356892983.19248.82.camel@aeonflux \
    --to=marcel@holtmann.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=pacho@gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox