Or an alternative patch might be just to delete this recipe altogether.
Its sole purpose is to work around defects in hardware which must be the
best part of a decade old and I would be slightly surprised if anyone
was still using DTL1s in this day and age.

p.

On Tue, 2011-07-05 at 16:52 +0100, Phil Blundell wrote:
> This one evaded the earlier mass removal due to extraneous trailing
> whitespace.
> 
> Signed-off-by: Phil Blundell <[email protected]>
> ---
>  .../bluez/bluez-dtl1-workaround_1.0.bb             |    3 +--
>  1 files changed, 1 insertions(+), 2 deletions(-)
> 
> diff --git a/meta/recipes-connectivity/bluez/bluez-dtl1-workaround_1.0.bb 
> b/meta/recipes-connectivity/bluez/bluez-dtl1-workaround_1.0.bb
> index b6b3d7d..103cfd9 100644
> --- a/meta/recipes-connectivity/bluez/bluez-dtl1-workaround_1.0.bb
> +++ b/meta/recipes-connectivity/bluez/bluez-dtl1-workaround_1.0.bb
> @@ -1,8 +1,7 @@
>  DESCRIPTION = "A nasty hack for for dtl1-cs driver to workaround 
> suspend/resume."
>  LICENSE = "GPLv2"
>  LIC_FILES_CHKSUM = "file://COPYING;md5=393a5ca445f6965873eca0259a17f833"
> -SECTION = "console" 
> -PRIORITY = "optional" 
> +SECTION = "console"
>  PR = "r3"
>   
>  SRC_URI = "file://02dtl1_cs.sh \



_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Reply via email to