Hi,

In the following linux-xlnx-3.8.bbappend, 

http://git.yoctoproject.org/cgit/cgit.cgi/meta-xilinx-community/tree/recipes-kernel/linux/linux-xlnx_3.8.bbappend

ZX3_ZYNQ7_PATCHSET = " \
                        file://zx3-zynq7/0001-ze7000-phy-micrel-phy-init.patch  
                            \
                        
file://zx3-zynq7/0002-ze7000-phy-adapt-marvell-settings.patch                   
    \
                        
file://zx3-zynq7/0003-zynq-nand-do-not-wait-on-erase-completion-in-cmd-fct.patch
    \
                        
file://zx3-zynq7/0004-clk-remove-clock-notifier-at-unregister.patch             
    \
                        
file://zx3-zynq7/0005-xdevcfg-Make-sure-that-devcfg-is-not-in-loopback-mod.patch
    \
                        
file://zx3-zynq7/0006-xilinx_emacps-Make-phy-address-configurable.patch         
    \
                        
file://zx3-zynq7/0007-kernel-sdhci-add-sd-card-support.patch                    
    \
                        
file://zx3-zynq7/0008-xilinx_emacps-Changed-change_mtu-so-that-it-is-possi.patch
    \
                        
file://zx3-zynq7/0009-xilinx_emacps-Set-the-maximum-frame-reception-size-t.patch
    \
                        "

PATCH_LIST_ze7000-zynq7 = "${ZX3_ZYNQ7_PATCHSET}”

<snip>

SRC_URI_append += " ${PATCH_LIST}”

<snip>

I get the following error, for all other machines, except for machine 
ze7000-zynq7:

ERROR: ExpansionError during parsing 
/tool/yocto/meta-xilinx/recipes-kernel/linux/linux-xlnx_3.8.bb: Failure 
expanding variable do_fetch[file-checksums], expression was 
${@bb.fetch.get_checksum_file_list(d)} which triggered exception MalformedUrl: 
The URL: '${PATCH_LIST}' is invalid and cannot be interpreted

If I redefine 

SRC_URI_append += " ${PATCH_LIST_ze7000-zynq7}”

it fixes the issue. 

However, I was wondering what is the correct way, to use the kernel PATCH_LIST 
variable?

Regards,

Elvis Dowson

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

-- 
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

Reply via email to