IRC log for #elinux on 20080827

00:33.45*** join/#elinux thraxisp (n=thraxisp@24.139.16.154)
00:44.25*** join/#elinux landley (n=landley@cpe-70-116-30-223.austin.res.rr.com)
04:57.01CapnKernelStill having trouble getting Linux to recognise the AT45DB642 dataflash on my AT91SAM9260-EK board... :-(
05:04.23CapnKernelhttp://www.pastebin.ca/1186028
05:09.00CapnKernelI can see that dataflash_init() is being called.
05:09.28CapnKernelIn the "other" webpage I quoted, what causes the SPI code to find the dataflash?
05:37.20*** join/#elinux pleemans (n=peter@dD577D009.access.telenet.be)
06:04.11CapnKernelHello, anyone here?
06:15.52HcEjupp
06:40.36CapnKernelSorry, back now.
06:40.45CapnKernelI'm still having trouble getting Linux to recognise the AT45DB642 dataflash on my AT91SAM9260-EK board.
06:40.54CapnKernelhttp://www.pastebin.ca/1186028
06:41.37HcEmtd_dataflash spi0.1: AT45DB642x (8448 KBytes)
06:41.40HcEseems good
06:43.53CapnKernelHans-Christian, the other day you asked me "do you have a spi_board_info struct in your board code".  The answer is yes, in arch/arm/mach-at91/board-sam9260ek.c.
06:45.06*** join/#elinux landley (n=landley@cpe-70-116-30-223.austin.res.rr.com)
06:46.09HcECapnKernel: 1) could you post your board code and kernel .config on pastebin? 2) Please use HcE to prefix me, since my IRC client will highlight the line then
06:48.14CapnKernelCan you please explain "Please use HcE to prefix me"?  (IRC/Pastebin newbie)
06:48.26CapnKernelHcE: Like this?
06:48.57HcECapnKernel: correct :)
06:49.22HcEthen my IRC client gives your nick a nice shiny yellow colour instead of the dull light grey ;)
06:52.23CapnKernelHcE: http://www.pastebin.ca/1186097  .  Board code is from stock 2.6.26.3: http://lxr.linux.no/linux+v2.6.26.3/arch/arm/mach-at91/board-sam9260ek.c#L120
06:54.21CapnKernelThe dataflash code is here: http://lxr.linux.no/linux+v2.6.26.3/drivers/mtd/devices/mtd_dataflash.c#L615
06:54.58CapnKernelI have put printks on all the functions in mtd_dataflash.c.  The only function that gets called is dataflash_init.  dataflash_probe never gets called.
06:56.57HcECapnKernel: You have defined CONFIG_MMC_AT91, and this rules out the DataFlash part of the board code
06:57.27CapnKernelThank you.
07:07.10CapnKernelHcE: Any ideas of what to try for the before-colon part of mtdparts=?  (About to try mtd_dataflash)
07:08.30HcEhuh?
07:10.58CapnKernelYay, working much better now: mtd_dataflash spi0.1: AT45DB642x (8448 KBytes)
07:12.29CapnKernelI still have to work out how to drive the cmdline mtdparts= parameter.  But I will try that tomorrow.
07:12.34CapnKernelThanks so much for your help!
07:12.49CapnKernelHow did you know that CONFIG_MMC_AT91 turns off the dataflash?
07:13.20CapnKernelOh I see, the "#if !defined(CONFIG_MMC_AT91)"
07:14.01CapnKernelHcE: Much appreciated.  Home time for me now.
07:29.45*** join/#elinux hw__ (n=hw@p578b3905.dip0.t-ipconnect.de)
07:38.22HcECapnKernel: home time?? I just came to work :(
07:51.58*** join/#elinux lyakh (n=lyakh@p57BD2509.dip0.t-ipconnect.de)
08:00.16*** join/#elinux lyakh (n=lyakh@p57BD0638.dip0.t-ipconnect.de)
12:59.21*** join/#elinux Redhatter (n=vk4fsjl@2001:388:f000:0:0:0:0:279)
13:12.11*** join/#elinux prpplague (n=dave@mail.americanmicrosystems.com)
13:17.35*** join/#elinux GPSFan (n=kenm@12.10.255.246)
14:18.49*** join/#elinux thraxisp (n=thraxisp@century.precidia.com)
15:15.53*** join/#elinux CheBuzz (n=CheBuzz@213-209-244.netrun.cytanet.com.cy)
15:16.00CheBuzzIf I have a device running Linux that has been "Tivoized", is there anyway to access the firmware stored on the flash?  I have root access to the machine.
15:40.28*** join/#elinux CheBuzz (n=CheBuzz@213-209-244.netrun.cytanet.com.cy)
15:45.42*** join/#elinux Sascha (n=sisawess@cssun.rrze.uni-erlangen.de)
16:18.49*** join/#elinux thraxisp_ (n=thraxisp@century.precidia.com)
16:39.30*** join/#elinux sifi (n=sifi@dhcp-254-233-206.biosci.ohio-state.edu)
18:13.01*** join/#elinux sjhill (n=sjhill@real.realitydiluted.com)
18:53.17*** join/#elinux emil|k (n=emil@e179235215.adsl.alicedsl.de)
18:59.14prpplagueCheBuzz: there a number of ways to access the system, it is generally dependent on the processor type and features
23:43.18*** join/#elinux thraxisp (n=thraxisp@24.139.16.154)
23:52.41*** join/#elinux AD-N770 (n=jep@24.Red-80-26-22.staticIP.rima-tde.net)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.