Re: [microblaze-uclinux] Re: Boa + SSL hanging after certificate download

[Paul Hartke <phartke@xxxxxxxxxxxx>]

The XUPV2P board doesn't have any flash onboard so the value for this option
doesn't do much.  Set it to anything reasonable as you already did.

You are hitting some versionitis.  The kernel included in the XUPV2P zip
file was compiled on July 9th.  The mb_auto.c file
http://cvs.uclinux.org/cgi-bin/cvsweb.cgi/uClinux-2.4.x/drivers/mtd/maps/mb_auto.c
that is causing these warnings wasn't even in CVS then.  In the XUPV2P
microblaze uclinux zip, there should probably be the date tag of the
checkout so that it could be completely reproduced.  Perhaps that's
something Jason Wu can discuss in his most excellent tutorial since its
becoming the main source for folks new to microblaze uclinux.  Those folks
that are creating zips and reference designs for boards can then include
the specific date of the cvs checkout/update in order for downstream folks
to completely reproduce the results.  Once they are comfortable with that,
the user can then update straight off cvs HEAD to get the latest if they so
desire.

Not sure the best way to handle the FLASH issue moving forward--if there is
no flash then I guess mtd doesn't need to be compiled at all.  The
uclinux-auto structure would be the one to handle this inside Linux itself.
 Alternatively, the EDK uClinux BSP package MLD/TCL could be changed to
enforce that these flash variables are always set.  John Williams will
probably comment on his preference/intention.

Paul

Quoting Jonathan Jung <jwjung@xxxxxxxxxxxxx>:
> --------------------------
>
> Another question I have regarding the building of the image...
>
> A few weeks ago, when I downloaded the package for my XUPV2P board, I
> could not build linux.  It would error out with an error related to
> not having CONFIG_XILINX_FLASH_SIZE and CONFIG_XILINX_FLASH_START
> defined (during mtd* compilation).  The included auto-config.in
> inside the microblaze_0 directory included with the XUP package
> didn't include this variable.
>
> I simple entered in some values to make it happy, it didn't seem like
> they overran any other memory locations:
>
> define_hex CONFIG_XILINX_FLASH_START 0xff000000
> define_hex CONFIG_XILINX_FLASH_SIZE 0x00800000
>
> This allowed the compilation to continue, and I had not noticed any
> problems playing around with various other facets of the distribution.
>
> Is there a .config that was used when creating the XUPV2P package on
> the webpage that I can use that won't ask for these variables?  They
> aren't specified when rebuilding the included system in the EDK, so I
> don't know what else to do with them other than to stub them out.
>
> Thanks,
>
> Jonathan
>
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/