All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Debian testing required: bcm203x firmware
Date: Fri, 12 Nov 2004 18:55:19 +0100	[thread overview]
Message-ID: <1100282119.7349.3.camel@pegasus> (raw)
In-Reply-To: <1100268649.8785.43.camel@saag>

Hi Edd,

> > > the firmware files are in the wrong place. You are using the old
> > > directory. They must be under /lib/firmware/.
> 
> OK, I renamed it to bluez-firmware and changed the location back
> to /lib/firmware.  bluez-utils-2.10-4 also updated to reference the
> right firmware package name.

the bluez-bcm203x package cannot depend on the non-free bluez-firmware
package, right?

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users/listinfo/bluez-users

  reply	other threads:[~2004-11-12 17:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-12 11:57 [Bluez-users] Debian testing required: bcm203x firmware Edd Dumbill
2004-11-12 12:13 ` Marcel Holtmann
2004-11-12 13:52   ` Edd Dumbill
2004-11-12 14:10     ` Edd Dumbill
2004-11-12 17:55       ` Marcel Holtmann [this message]
2004-11-12 18:52         ` Edd Dumbill
2004-11-12 19:01           ` Marcel Holtmann
2004-11-12 22:52             ` Edd Dumbill
2004-11-13  0:37               ` Marcel Holtmann
2004-11-12 14:17     ` Marcel Holtmann

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=1100282119.7349.3.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    /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.