Sign In

Don't have a Xilinx account yet?

  • Choose to receive important news and product information
  • Gain access to special content
  • Personalize your web experience on Xilinx.com

Create Account

Username

Password

Forgot your password?
XClose Panel
Xilinx Home
Reply
Regular Contributor
beandigital
Posts: 98
Registered: ‎04-27-2010
0

menuconfig

I am looking at developing a SATA driver. When I use menuconfig with version 3 of the kernel all of the SCSI driver options are gone. Is there a way to get them back?

 

Thanks

 

Jon

Super Contributor
norman_wong
Posts: 143
Registered: ‎05-28-2012
0

Re: menuconfig

I've no problems with accessing the SCSI menu so far. I am using the tree from linux-xlnx GIT, build3-trd tag. On my platform:

make ARCH=arm xilinx_zynq_defconfig

make ARCH=arm menuconfig

 

Regular Contributor
beandigital
Posts: 98
Registered: ‎04-27-2010
0

Re: menuconfig

I'm using Microblaze, don't know if that matters.

Super Contributor
norman_wong
Posts: 143
Registered: ‎05-28-2012
0

Re: menuconfig

Which default config are you using? From what I can see in the Xilinx GIT, CONFIG_BLOCK was removed from most of the configs in 2010-08-14. The SCSI and lot other stuff was dependent on this config setting. The xilinx_mmu_defconfig looks okay. Just guesses.

Regular Contributor
beandigital
Posts: 98
Registered: ‎04-27-2010
0

Re: menuconfig

I'm using the sp605 config and then altering it to match my hardware. Not being a Linux expert can you tell me what determines the menu items when menuconfig is used?

Super Contributor
norman_wong
Posts: 143
Registered: ‎05-28-2012
0

Re: menuconfig

I'm no expert either and I'm not familiar with the Microblaze platform. My comments are from tracing the Kconfigs in the kernel at the Xilinx GIT.

arch/microblaze/Kconfig - Config template for all microblaze boards.
drivers/Kconfig - sourced by above
drivers/scsi/Kconfig - sourced by above. Note depends requirements.

arch/microblaze/configs/sp605_le_defconfig
- Board specific. Order of values listed should match definitions in arch/microblaze/Kconfig. You could try directly enabling BLOCK by changing the line
# CONFIG_BLOCK is not set
to
CONFIG_BLOCK=y
The xilinx_mmu_defconfig seems to okay with setting it. There should be a ""Enable the block layer"" in the menuconfig but I can't seem to find an "source block/Kconfig". Probably in another Kconfig file.

Regular Contributor
beandigital
Posts: 98
Registered: ‎04-27-2010
0

Re: menuconfig

I will try experimenting and see what I can do.

 

Thanks

 

Jon