element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      • Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Vietnam
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Avnet Boards Forums
  • Products
  • Dev Tools
  • Avnet & Tria Boards Community
  • Avnet Boards Forums
  • More
  • Cancel
Avnet Boards Forums
Mini-ITX Hardware Design Build the Linux kernel (uImage) in the PCIe Root Complex Design
  • Forum
  • Documents
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Avnet Boards Forums to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Not Answered
  • Replies 1 reply
  • Subscribers 334 subscribers
  • Views 555 views
  • Users 0 members are here
Related

Build the Linux kernel (uImage) in the PCIe Root Complex Design

Former Member
Former Member over 11 years ago

Hi,

I follow the instructions in the PCIe root complex design 2014.2 on the mini-ITX board in order to build the Linux kernel. But I have two problems now.


First, I download the kernel from
git://github.com/Xilinx/linux-xlnx.git
I check the kernel version and it is 3.14

After i have applied the patch,
git am zynq_rc_nwl_drivers.patch
the kernel version is changed to 3.9,

so is it a correct result that the kernel version changes?


Second, since i want to use this PCIe RC design to control a solid state disk, i add the SATA and ACHI drivers in the menuconfig as follows,

make ARCH=arm zc706_rc_defconfig
make ARCH=arm menuconfig

after i have added the SATA drviers, I build the kernel by
make ARCH=arm uImage -j 4 UIMAGE_LOADADDR=0x8000

However, a lot of options jump out as follows:



hadoop@cubiemaster:~/kernel/linux-xlnx$ git apply --check zynq_rc_nwl_drivers.patch
hadoop@cubiemaster:~/kernel/linux-xlnx$ git am zynq_rc_nwl_drivers.patch
Applying: K7 Base and Connectivity TRD versions of North West Logic DMA drivers
/home/hadoop/kernel/linux-xlnx/.git/rebase-apply/patch:3273: trailing whitespace.
obj-y += xdma/ xrawdata0/
/home/hadoop/kernel/linux-xlnx/.git/rebase-apply/patch:5201: trailing whitespace.
ccflags-y  := -DK7_TRD -DX86_PC -DNWLDMA -DXENV_LINUX -DUSE_IO_MACROS -DXLITTLE_ENDIAN -DPCI_LINUX -I arch/arm/mach-zynq/k7_base_driver/include/
/home/hadoop/kernel/linux-xlnx/.git/rebase-apply/patch:5371: trailing whitespace.
   spin_lock(&(InstancePtr->bdring_lock));
/home/hadoop/kernel/linux-xlnx/.git/rebase-apply/patch:5422: trailing whitespace.
   spin_unlock(&(InstancePtr->bdring_lock));
/home/hadoop/kernel/linux-xlnx/.git/rebase-apply/patch:5933: trailing whitespace.
extern spinlock_t GlobalDataLock;
warning: squelched 959 whitespace errors
warning: 964 lines add whitespace errors.
hadoop@cubiemaster:~/kernel/linux-xlnx$ make ARCH=arm zc706_rc_defconfig
  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/kconfig/conf.o
  SHIPPED scripts/kconfig/zconf.tab.c
  HOSTCC  scripts/kconfig/zconf.tab.o
  HOSTLD  scripts/kconfig/conf
#
# configuration written to .config
#
hadoop@cubiemaster:~/kernel/linux-xlnx$ make menuconfig
  HOSTCC  scripts/kconfig/lxdialog/checklist.o
  HOSTCC  scripts/kconfig/lxdialog/inputbox.o
  HOSTCC  scripts/kconfig/lxdialog/menubox.o
  HOSTCC  scripts/kconfig/lxdialog/textbox.o
  HOSTCC  scripts/kconfig/lxdialog/util.o
  HOSTCC  scripts/kconfig/lxdialog/yesno.o
  HOSTCC  scripts/kconfig/mconf.o
  HOSTLD  scripts/kconfig/mconf
scripts/kconfig/mconf Kconfig
configuration written to .config

*** End of the configuration.
*** Execute 'make' to start the build or try 'make help'.
hadoop@cubiemaster:~/kernel/linux-xlnx$ make ARCH=arm uImage -j 4 UIMAGE_LOADADDR=0x8000
scripts/kconfig/conf --silentoldconfig Kconfig
*
* Restart config...
*
*
* IRQ subsystem
*
Expose hardware/virtual IRQ mapping via debugfs (IRQ_DOMAIN_DEBUG) [N/y/?] (NEW)
*
* General setup
*
Cross-compiler tool prefix (CROSS_COMPILE) []
Local version - append to kernel release (LOCALVERSION) [-xilinx] -xilinx
Automatically append version information to the version string (LOCALVERSION_AUTO) [Y/n/?] y
Kernel compression mode
> 1. Gzip (KERNEL_GZIP)
  2. LZMA (KERNEL_LZMA)
  3. XZ (KERNEL_XZ)
  4. LZO (KERNEL_LZO)
choice[1-4?]: 1
Default hostname (DEFAULT_HOSTNAME) [(none)] (none)
Support for paging of anonymous memory (swap) (SWAP) [Y/n/?] y
System V IPC (SYSVIPC) [Y/n/?] y
POSIX Message Queues (POSIX_MQUEUE) [N/y/?] n
open by fhandle syscalls (FHANDLE) [N/y/?] n
Auditing support (AUDIT) [N/y/?] n
Kernel .config support (IKCONFIG) [Y/n/m/?] y
  Enable access to .config through /proc/config.gz (IKCONFIG_PROC) [Y/n/?] y
Kernel log buffer size (16 => 64KB, 17 => 128KB) (LOG_BUF_SHIFT) [14] 14
Checkpoint/restore support (CHECKPOINT_RESTORE) [N/y/?] n
Require conversions between uid/gids and their internal representation (UIDGID_STRICT_TYPE_CHECKS) [N/y/?] n
Automatic process group scheduling (SCHED_AUTOGROUP) [N/y/?] n
Enable deprecated sysfs features to support old userspace tools (SYSFS_DEPRECATED) [Y/n/?] y
  Enable deprecated sysfs features by default (SYSFS_DEPRECATED_V2) [Y/n/?] y
Kernel->user space relay support (formerly relayfs) (RELAY) [N/y/?] n
Initial RAM filesystem and RAM disk (initramfs/initrd) support (BLK_DEV_INITRD) [Y/n/?] y
  Initramfs source file(s) (INITRAMFS_SOURCE) []
  Support initial ramdisks compressed using gzip (RD_GZIP) [Y/n/?] y
  Support initial ramdisks compressed using bzip2 (RD_BZIP2) [N/y/?] n
  Support initial ramdisks compressed using LZMA (RD_LZMA) [N/y/?] n
  Support initial ramdisks compressed using XZ (RD_XZ) [N/y/?] n
  Support initial ramdisks compressed using LZO (RD_LZO) [N/y/?] n
Optimize for size (CC_OPTIMIZE_FOR_SIZE) [Y/n/?] y
Enable 16-bit UID system calls (UID16) [Y/n/?] (NEW)




It seems that it is not config properly...
I don't know if i have made any operations incorrectly?

Any suggestions will be appreciated!
Thank You!



  • Sign in to reply
  • Cancel
  • Former Member
    0 Former Member over 11 years ago

    if you use petalinux 2014.2 and DO NOT APPLY any patches you should get at least as far I getting lspci to work, that would be first step.. to get started.

    https://wiki.trenz-electronic.de/display/ToT/Petalinux+PCIe+step+by+step

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube