flashrom September 2013

flashrom@flashrom.org

25 participants
142 discussions

[PATCH] squash! BSD refinements.
by Stefan Tauner 10 Sep '13

10 Sep '13

Also, fix date handling in getrevision.sh to work with the various formats for invoking 'date'. This also uses svn's info --xml output instead of the regular one. Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> --- Together with my previous patch I would also like to fix the getrevision script as follows. The commit log and inline comments explain how precisely. util/getrevision.sh | 36 +++++++++++++++++++++++++++++++----- 1 file changed, 31 insertions(+), 5 deletions(-) diff --git a/util/getrevision.sh b/util/getrevision.sh index c05f59e..5fd83f5 100755 --- a/util/getrevision.sh +++ b/util/getrevision.sh @@ -110,15 +110,31 @@ scm_url() { timestamp() { local t + # date syntaxes are manifold: + # gnu date [-d input]... [+FORMAT] + # netbsd date [-ajnu] [-d date] [-r seconds] [+format] [[[[[[CC]yy]mm]dd]HH]MM[.SS]] + # freebsd date [-jnu] [-d dst] [-r seconds] [-f fmt date | [[[[[cc]yy]mm]dd]HH]MM[.ss]] [+format] [...] + # dragonflybsd date [-jnu] [-d dst] [-r seconds] [-f fmt date | [[[[[cc]yy]mm]dd]HH]MM[.ss]] [+format] [...] + # openbsd date [-aju] [-d dst] [-r seconds] [+format] [[[[[[cc]yy]mm]dd]HH]MM[.SS]] [...] if svn_is_file_tracked "$2" ; then if svn_has_local_changes "$2"; then t=$(date -u "$1") else # No local changes, get date of the last log record. - local last_commit_date="$(svn info "$2" | \ - grep '^Last Changed Date:' | \ - awk '{print $4" "$5" "$6}')" - t=$(date -d "${last_commit_date}" -u "$1") + local last_commit_date="$(svn info --xml "$2"| \ + sed -n -e 's/<date>$.*$<\/date>/\1/p' -e 's/\..*Z/Z/p')" + + case $(uname) in + # Most BSD dates do not support parsing date values from user input with -d but all of + # them support parsing the syntax with [[[[[[cc]yy]mm]dd]HH]MM[.ss]]. We have to + # transform the ISO8601 date first though. + NetBSD|OpenBSD|DragonFly|FreeBSD) + last_commit_date="$(echo ${last_commit_date} | \ + sed -n -e 's/$....$-$..$-$..$T$..$:$..$:$..$Z/\1\2\3\4\5\.\6/p')" + t=$(date -u -j "${last_commit_date}" "$1" 2>/dev/null);; + *) + t=$(date -u -d "${last_commit_date}" "$1" 2>/dev/null);; + esac fi elif git_is_file_tracked "$2" ; then # are there local changes? @@ -126,12 +142,22 @@ timestamp() { t=$(date -u "${1}") else # No local changes, get date of the last commit - t=$(date -d "$(git log --pretty=format:"%cD" -1 -- "$2")" -u "$1") + case $(uname) in + # Most BSD dates do not support parsing date values from user input with -d but all of + # them support parsing epoch seconds with -r. Thanks to git we can easily use that: + NetBSD|OpenBSD|DragonFly|FreeBSD) + t=$(date -u -r "$(git log --pretty=format:%ct -1 -- $2)" "$1" 2>/dev/null);; + *) + t=$(date -d "$(git log --pretty=format:%cD -1 -- $2)" -u "$1" 2>/dev/null);; + esac fi else t=$(date -u "$1") fi + if [ -z "$t" ]; then + echo "Warning: Could not determine timestamp." 2>/dev/null + fi echo "${t}" } -- Kind regards, Stefan Tauner

1 0

Re: [flashrom] [PATCH 2/6] sbxxx: Set SPI clock to 16.5 MHz and disable fast reads.
by Carl-Daniel U. Hailfinger 10 Sep '13

10 Sep '13

[Sorry for breaking the threading. This is a reply to http://patchwork.coreboot.org/patch/4011/ ] Stefan Tauner wrote on 2013-08-14 17:44:19 > > On Wed, 14 Aug 2013 08:56:27 +0200 > Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> wrote: > > > Am 10.08.2013 03:45 schrieb Stefan Tauner: > > > diff --git a/sb600spi.c b/sb600spi.c > > > index c9be44c..2c1d400 100644 > > > --- a/sb600spi.c > > > +++ b/sb600spi.c > > > @@ -272,6 +272,61 @@ static int sb600_spi_send_command(struct flashctx *flash, unsigned int writecnt, > > > return 0; > > > } > > > > > > +struct spispeed { > > > + const char *const name; > > > + const int8_t speed; > > > +}; > > > + > > > +static const struct spispeed spispeeds[] = { > > > + { "66 MHz", 0x00 }, > > > + { "33 MHz", 0x01 }, > > > + { "22 MHz", 0x02 }, > > > + { "16.5 MHz", 0x03 }, > > > +}; > > > I see struct spispeed and think it is a somewhat odd construct. The > > speed member is just the array index stored in the corresponding array > > member. Do you envision speed values which are not an array index? > > I want to merge the various frequency setting functions eventually and > Dediprog for example uses non-linear values. Hence I'd rather use this > unnecessary scheme for easier refactoring later. OK. > > > +static int set_speed(struct pci_dev *dev, const struct spispeed *spispeed) > > > +{ > > > + bool success = false; > > > + uint8_t speed = spispeed->speed; > > > + > > > + msg_pdbg("Setting SPI clock to %s (0x%x).\n", spispeed->name, speed); > > > + if (amd_gen != CHIPSET_YANGTZE) { > > > + rmmio_writeb((mmio_readb(sb600_spibar + 0xd) & ~(0x3 << 4)) | (speed << 4), sb600_spibar + 0xd); > > > + success = (speed == ((mmio_readb(sb600_spibar + 0xd) >> 4) & 0x3)); > > > The code reads spispeed and then sets 16 MHz regardless of whether it's > > already 16 MHz. I also seem to remember that you were opposed to setting > > this speed permanently and advocated to restore it on shutdown. > > This should not be done unconditionally, right, I will change this. > But it is done (like the (un)setting of fast speed also) with the > r*-mmio functions so it should be reverted on shutdown AFAIK? Indeed, I overlooked the r* prefix. Given that a repost of part 1 of this series would be nice, I'll go out on a limb and ask you to repost this one after the changes as well. With the change you mentioned, this is Acked-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Regards, Carl-Daniel

1 0

Re: [flashrom] [PATCH 1/6] sbxxx: Add detection for the remaining AMD chipset families.
by Carl-Daniel U. Hailfinger 10 Sep '13

10 Sep '13

[Sorry for breaking the threading. This is meant to be a reply to http://patchwork.coreboot.org/patch/4016/ ] Stefan Tauner wrote on 2013-08-14 17:35:13 > > On Wed, 14 Aug 2013 08:42:15 +0200 > Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> wrote: > > > Am 10.08.2013 03:45 schrieb Stefan Tauner: > > > Also, correct prettyprinting of the registers of the various families, > > > and abort if SpiAccessMacRomEn or SpiHostAccessRomEn prohibit full access. > > > > > > Tested reading/writing on ASRock IMB-A180, and chipset detection on > > > one of each affected generation by Chris Goodrich from Sage. > > > > > > Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> > > > --- > > > sb600spi.c | 133 ++++++++++++++++++++++++++++++++++++++++++++++++------------- > > > 1 file changed, 106 insertions(+), 27 deletions(-) > > > > > > diff --git a/sb600spi.c b/sb600spi.c > > > index cb7c4ac..c9be44c 100644 > > > --- a/sb600spi.c > > > +++ b/sb600spi.c > > > @@ -57,7 +57,28 @@ static enum amd_chipset amd_gen = CHIPSET_AMD_UNKNOWN; > > > static void determine_generation(struct pci_dev *dev) > > > { > > > amd_gen = CHIPSET_AMD_UNKNOWN; > > > - if (dev->device_id == 0x780e) { > > > + msg_pdbg2("Trying to determine the generation of the SPI interface... "); > > > + if (dev->device_id == 0x438d) { > > > + amd_gen = CHIPSET_SB6XX; > > > + msg_pdbg("SB6xx detected.\n"); > > > + } else if (dev->device_id == 0x439d) { > > > + struct pci_dev *smbus_dev = pci_dev_find(0x1002, 0x4385); > > > > Why do we search twice for this SMBus device, once inside > > sb600_probe_spi and once here? Can't we just pass the smbus device as > > second parameter to determine_generation? > > Yes we could and I thought about this too but came to the conclusion > that it is not worth it. Do you think otherwise? I'd really like to limit the number of times we search for PCI devices. On some machines with lots of PCI devices that can take a lot of time. That said, I also think such refactoring can be done in a later iteration, and it is also possible to have the generation detection as first command inside the AMD SBx00 SPI probe function, and let it set a static struct *smbus_dev. Your choice when/how to deal with it. Anyway, most/all of the code above was committed in r1706, so this is mostly an after-the-fact review. > > > + if (smbus_dev == NULL) > > > + return; > > > + uint8_t rev = pci_read_byte(smbus_dev, PCI_REVISION_ID); > > > + if (rev >= 0x39 && rev <= 0x3D) { > > > + amd_gen = CHIPSET_SB7XX; > > > + msg_pdbg("SB7xx/SP5100 detected.\n"); > > > + } else if (rev >= 0x40 && rev <= 0x42) { > > > + amd_gen = CHIPSET_SB89XX; > > > + msg_pdbg("SB8xx/SB9xx/Hudson-1 detected.\n"); > > > + } else { > > > + msg_pwarn("SB device found but SMBus revision 0x%02x does not match known values.\n" > > > + "Assuming SB8xx/SB9xx/Hudson-1. Please send a log to flashrom(a)flashrom.org\n", > > > + rev); > > > + amd_gen = CHIPSET_SB89XX; > > > > We could error out here as well. The next release is a few weeks away > > anyway. > > No regressions if we can easily avoid them please (I'll break enough > stuff unintentionally, rest assured :) > It is fairly safe to assume that the code path for sb89xx/hudson will > work on such devices if they exist, maybe with some wrong prints if it > is sb7xx but nothing we worried about until I provided a solution for > it in most cases :) I'm not convinced that this would likely introduce a regression. For all we know, AMD might use higher SMBus device PCI revision IDs for respins of older chipsets, and there we really want to error out instead of having flashrom deal with bogus errors. > > > + } > > > + } else if (dev->device_id == 0x780e) { > > > /* The PCI ID of the LPC bridge doesn't change between Hudson-2/3/4 and Yangtze (Kabini/Temash) > > > * although they use different SPI interfaces. */ > > > #ifdef USE_YANGTZE_HEURISTICS > > > @@ -94,7 +115,11 @@ static void determine_generation(struct pci_dev *dev) > > > "the output of lspci -nnvx, thanks!.\n", rev); > > > } > > > #endif > > > - } > > > + } else > > > + msg_pwarn("%s: Unknown LPC device %" PRIx16 ":%" PRIx16 ".\n" > > > + "Please report this to flashrom(a)flashrom.org and include this log and\n" > > > + "the output of lspci -nnvx, thanks!\n", > > > + __func__, dev->vendor_id, dev->device_id); > > > } > > > > > > static void reset_internal_fifo_pointer(void) > > > @@ -250,7 +275,7 @@ static int sb600_spi_send_command(struct flashctx *flash, unsigned int writecnt, > > > static int sb600_handle_imc(struct pci_dev *dev, bool amd_imc_force) > > > { > > > /* Handle IMC everywhere but sb600 which does not have one. */ > > > - if (dev->device_id == 0x438d) > > > + if (amd_gen == CHIPSET_SB6XX) > > > return 0; > > > > > > /* TODO: we should not only look at IntegratedImcPresent (LPC Dev 20, Func 3, 40h) but also at > > > @@ -334,6 +359,12 @@ int sb600_probe_spi(struct pci_dev *dev) > > > sb600_spibar += tmp & 0xfff; > > > > > > determine_generation(dev); > > > + if (amd_gen == CHIPSET_AMD_UNKNOWN) { > > > + /* FIXME: Eventually this should be a fatal error, but until we are certain to have covered all > > > + * IDs actually found in the wild, try to mimmick the previous behavior. */ > > > > Given that we're now post-0.9.7, we can make this a fatal error. > > Besides that, the current patch doesn't even set CHIPSET_AMD_UNKNOWN for > > some combinations with unknown SMBus PCI revision ID. > > Sure, this was targeted to be in 0.9.7 (and see above). > > > > + msg_pwarn("Could not determine chipset generation. Assuming SB6xx."); > > > + amd_gen = CHIPSET_SB6XX; > > > + } > > > > > > if (amd_gen == CHIPSET_YANGTZE) { > > > msg_perr("SPI on Kabini/Temash and newer chipsets are not yet supported.\n" > > > @@ -341,35 +372,83 @@ int sb600_probe_spi(struct pci_dev *dev) > > > return ERROR_NONFATAL; > > > } > > > > > > - tmp = pci_read_long(dev, 0xa0); > > > - msg_pdbg("AltSpiCSEnable=%i, SpiRomEnable=%i, " > > > - "AbortEnable=%i\n", tmp & 0x1, (tmp & 0x2) >> 1, > > > - (tmp & 0x4) >> 2); > > > - tmp = (pci_read_byte(dev, 0xba) & 0x4) >> 2; > > > - msg_pdbg("PrefetchEnSPIFromIMC=%i, ", tmp); > > > - > > > - tmp = pci_read_byte(dev, 0xbb); > > > - /* FIXME: Set bit 3,6,7 if not already set. > > > - * Set bit 5, otherwise SPI accesses are pointless in LPC mode. > > > - * See doc 42413 AMD SB700/710/750 RPR. > > > + /* Chipset support matrix for SPI Base_Addr (LPC PCI reg 0xa0) > > > + * bit 6xx 7xx/SP5100 8xx 9xx hudson1 hudson2+ yangtze > > > + * 3 rsvd <- <- ? <- ? RouteTpm2Spi > > > + * 2 rsvd AbortEnable rsvd ? <- ? <- > > > + * 1 rsvd SpiRomEnable <- ? <- ? <- > > > + * 0 rsvd AltSpiCSEnable<1> rsvd ? <- ? <- > > > > Maybe it's just me, but I have trouble parsing that table. Let's talk > > about bit 2: What you mean is clear for 6xx (rsvd), 7xx (abortenable), > > 8xx (abortenable). I'm assuming that this bit is not described for 9xx > > and hudson1, but why is the hudson2+ entry "?" instead of "<-" ? Or do > > the "?" entries for 9xx and hudson2+ have a different meaning? > > Actually it is the <- that changes meaning, if you will, and the ? are > not just "we dont know", as one obviously would to infer. > The ? marks values where we do not have a datasheet, but which we > assume to be identical to the previous generations. So maybe we should > use "<-?" instead? Other suggestions are very welcomed. > Now it should also be clear what the <- after a ? means: we have a > datasheet and it indicates the same values as the generation *before* > the question marks before it. I used this mainly for myself but I would > still like to include it in some form. Let me try to phrase this in a way I can understand: +++++++++++++ How to read this table: "nd" means we have no datasheet for this chipset generation. "ni" means the datasheet for this generation doesn't have any relevant info. "<-" means the bit/register meaning is identical to the next non-ni/non-nd chipset to the left. If a "nd" chipset is between two chipsets with identical meaning, we assume the meaning didn't change twice in between, i.e. the meaning is unchanged for the "nd" chipset. This is a tried and (so far) valid assumption. +++++++++++++ Your "?" would turn into "nd". That said, keeping your symbols is also an option. My phrasing for that scenario would be: +++++++++++++ How to read this table: "?" means we have no datasheet for this chipset generation or the datasheet doesn't have any relevant info. "<-" means the bit/register meaning is identical to the next non-"?" chipset to the left. "<-" thus never refers to a "?". If a "?" chipset is between two chipsets with identical meaning, we assume the meaning didn't change twice in between, i.e. the meaning is unchanged for the "?" chipset. This is a tried and (so far) valid assumption. +++++++++++++ > > > + * > > > + * <1> It is unknown if that was ever working. On later chipsets the CS config is at memmapped 0x1D. > > > > Heh. Let's find someone with DualBIOS on a SB7xx board. But seriously, > > I'd assume this works if it's still in the current revision of the > > register reference guide. > > The problem is (IIRC) that it is not too well defined (who would have > thought that!) but maybe I am confusing it with Fast Speed. AFAICS the meaning is well defined, except that vendors apparently didn't use it on the boards we know. A simple test would be to set that bit and check if SPI probe still returns anything. If yes, there are either two flash chips or my understanding of that bit is wrong. > > > */ > > > - msg_pdbg("PrefetchEnSPIFromHost=%i, SpiOpEnInLpcMode=%i\n", > > > - tmp & 0x1, (tmp & 0x20) >> 5); > > > - tmp = mmio_readl(sb600_spibar); > > > - /* FIXME: If SpiAccessMacRomEn or SpiHostAccessRomEn are zero on > > > - * SB700 or later, reads and writes will be corrupted. Abort in this > > > - * case. Make sure to avoid this check on SB600. > > > + if (amd_gen >= CHIPSET_SB7XX) { > > > + tmp = pci_read_long(dev, 0xa0); > > > + msg_pdbg("SpiRomEnable=%i", (tmp >> 1) & 0x1); > > > + if (amd_gen == CHIPSET_SB7XX) > > > + msg_pdbg(", AltSpiCSEnable=%i, AbortEnable=%i", tmp & 0x1, (tmp >> 2) & 0x1); > > > + > > > + tmp = pci_read_byte(dev, 0xba); > > > + msg_pdbg(", PrefetchEnSPIFromIMC=%i", (tmp & 0x4) >> 2); > > > + > > > + tmp = pci_read_byte(dev, 0xbb); > > > + /* FIXME: Set bit 3,6,7 if not already set. > > > + * Set bit 5, otherwise SPI accesses are pointless in LPC mode. > > > + * See doc 42413 AMD SB700/710/750 RPR. > > > > Are these bits required to be set even for post-SB7000 chipsets? > > That's left as an exercise to the reader. :P > 5 is reserved anywhere but on sb7x/sp5100, the other bits change > semantics in sb8xx... > > > > + */ > > > + if (amd_gen == CHIPSET_SB7XX) > > > + msg_pdbg(", SpiOpEnInLpcMode=%i", (tmp >> 5) & 0x1); > > > + msg_pdbg(", PrefetchEnSPIFromHost=%i\n", tmp & 0x1); > > > + } > > > + > > > + /* Chipset support matrix for SPI_Cntrl0 (spibar + 0x0) > > > + * bit 6xx 7xx/SP5100 8xx 9xx hudson1 hudson2+ yangtze > > > + * 17 rsvd <- <- ? <- ? <- > > > > Again the table I don't understand. Maybe you should add an explanation > > which specifies the meaning of "?". > > Given the explanation above, would you mind formulating it? IMHO it > improves such things quite a bit if another mind puts it into words > than the one inventing it. Done, see above. > > > + * 18 rsvd <- fastReadEnable<1> ? <- ? SpiReadMode[0]<1> > > > + * 19 SpiArbEnable <- <- ? <- ? <- > > > + * 20 (FifoPtrClr) <- <- ? <- ? <- > > > + * 21 (FifoPtrInc) <- <- ? <- ? IllegalAccess > > > + * 22 SpiAccessMacRomEn <- <- ? <- ? <- > > > + * 23 SpiHostAccessRomEn <- <- ? <- ? <- > > > + * 24:26 ArbWaitCount <- <- ? <- ? <- > > > + * 27 SpiBridgeDisable <- <- ? <- ? rsvd > > > + * 28 rsvd DropOneClkOnRd = SPIClkGate ? <- ? <- > > > + * 29:30 rsvd <- <- ? <- ? SpiReadMode[2:1]<1> > > > + * 31 rsvd <- SpiBusy ? <- ? <- > > > + * > > > + * <1> see handle_speed > > > > Which handle_speed? Can't find it in svn HEAD nor in this patch. > > Added later in the patch set. Do you really want me to change those > lines again in the followup patch? It would have made review easier. > I had the impression you hate that :) Yes and no. While I try to avoid changing a line multiple times in a patchset, I also try to keep each patch self-contained. > > > */ > > > - msg_pdbg("(0x%08" PRIx32 ") fastReadEnable=%u, SpiArbEnable=%i, SpiAccessMacRomEn=%i, " > > > - "SpiHostAccessRomEn=%i, ArbWaitCount=%i, " > > > - "SpiBridgeDisable=%i, DropOneClkOnRd=%i\n", > > > - tmp, (tmp >> 18) & 0x1, > > > - (tmp >> 19) & 0x1, (tmp >> 22) & 0x1, > > > - (tmp >> 23) & 0x1, (tmp >> 24) & 0x7, > > > - (tmp >> 27) & 0x1, (tmp >> 28) & 0x1); > > > + tmp = mmio_readl(sb600_spibar + 0x00); > > > + msg_pdbg("(0x%08" PRIx32 ") SpiArbEnable=%i", tmp, (tmp >> 19) & 0x1); > > > + > > > + msg_pdbg(", SpiAccessMacRomEn=%i, SpiHostAccessRomEn=%i, ArbWaitCount=%i", > > > + (tmp >> 22) & 0x1, (tmp >> 23) & 0x1, (tmp >> 24) & 0x7); > > > + > > > + if (amd_gen != CHIPSET_YANGTZE) > > > + msg_pdbg(", SpiBridgeDisable=%i", (tmp >> 27) & 0x1); > > > + > > > + switch (amd_gen) { > > > + case CHIPSET_SB7XX: > > > + msg_pdbg(", DropOneClkOnRd/SpiClkGate=%i", (tmp >> 28) & 0x1); > > > > Should we check that bit and set it to 0? I haven't yet been able to > > find a good explanation of what it does, but it seems to be a trick to > > allow normal read commands at higher speed. I could be mistaken, though. > > I would refrain from changing it if we don't really know what it does > (and we probably will never do so...). I have read the description a > few times... and it does not make a lot of sense to me. Maybe our friends at AMD/Sage can explain this? > > > + case CHIPSET_SB89XX: > > > + case CHIPSET_HUDSON234: > > > + msg_pdbg(", SpiBusy=%i", (tmp >> 31) & 0x1); > > > + default: break; > > > + } > > > + msg_pdbg("\n"); > > > + > > > + if (((tmp >> 22) & 0x1) == 0 || ((tmp >> 23) & 0x1) == 0) { > > > + msg_perr("ERROR: State of SpiAccessMacRomEn or SpiHostAccessRomEn prohibits full access.\n"); > > > + return ERROR_NONFATAL; > > > + } > > > + > > > tmp = (mmio_readb(sb600_spibar + 0xd) >> 4) & 0x3; > > > msg_pdbg("NormSpeed is %s MHz\n", speed_names[tmp]); > > > > AFAICS this speed handling stuff is changing in a later patch, correct? > > Exactly because this is a good breaking point to avoid a monster > patch ;) > > Thanks for the review! Apart from the ? explanation and the fatal > error, I think this can go in soon? Yes, looks fine otherwise. Could you please forward-port this patch and repost it? I just want to make sure I didn't overlook anything serious. Otherwise, this is (with the ? explanation and the fatal error) Acked-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Regards, Carl-Daniel

1 0

Re: [flashrom] BCOM WinNET P680 patch
by Corey Osgood 09 Sep '13

09 Sep '13

It's one of those days, I guess. This is the correct version of the patch. On Sun, Sep 8, 2013 at 10:32 PM, Corey Osgood <corey.osgood(a)gmail.com>wrote: > And here's the patch! > > > On Sun, Sep 8, 2013 at 10:24 PM, Corey Osgood <corey.osgood(a)gmail.com>wrote: > >> This patch replaces Alex Mauer's previous patch for this board. Tested to >> read, erase, and write on 2 different boards, both with AMIC A29040BL flash >> chips, using both stock BIOS and coreboot images. Patch marks the AMIC chip >> as tested at the same time. >> >> Signed-off-by: Corey Osgood <corey.osgood(a)gmail.com> >> > >

1 0

Re: [flashrom] BCOM WinNET P680 patch
by Corey Osgood 09 Sep '13

09 Sep '13

And here's the patch! On Sun, Sep 8, 2013 at 10:24 PM, Corey Osgood <corey.osgood(a)gmail.com>wrote: > This patch replaces Alex Mauer's previous patch for this board. Tested to > read, erase, and write on 2 different boards, both with AMIC A29040BL flash > chips, using both stock BIOS and coreboot images. Patch marks the AMIC chip > as tested at the same time. > > Signed-off-by: Corey Osgood <corey.osgood(a)gmail.com> >

1 0

BCOM WinNET P680 patch
by Corey Osgood 09 Sep '13

09 Sep '13

This patch replaces Alex Mauer's previous patch for this board. Tested to read, erase, and write on 2 different boards, both with AMIC A29040BL flash chips, using both stock BIOS and coreboot images. Patch marks the AMIC chip as tested at the same time. Signed-off-by: Corey Osgood <corey.osgood(a)gmail.com>

1 0

Raspberry Pi Pm25LD010 output files
by Vasile Ceteras 07 Sep '13

07 Sep '13

A million thanks for this awesome tool, it worked like a charm! Vasile

1 0

[PATCH] DOS refinements.
by Stefan Tauner 06 Sep '13

06 Sep '13

This allows to use the DOS library trees stored in a user-specified directory. I have mirrored the needed patches, sources and binaries (the latter are properly licensed to allow that) in the flashrom wiki, so use those URLs instead of the original sources. Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> --- Makefile | 12 +++++++----- README | 20 ++++++++++++-------- 2 files changed, 19 insertions(+), 13 deletions(-) diff --git a/Makefile b/Makefile index de3cf97..29b5f1e 100644 --- a/Makefile +++ b/Makefile @@ -39,6 +39,7 @@ CFLAGS ?= -Os -Wall -Wshadow EXPORTDIR ?= . AR ?= ar RANLIB ?= ranlib +DOSLIBS_BASE ?= .. # The following parameter changes the default programmer that will be used if there is no -p/--programmer # argument given when running flashrom. The predefined setting does not enable any default so that every # user has to declare the programmer he wants to use on every run. The rationale for this to be not set @@ -109,11 +110,12 @@ endif ifeq ($(TARGET_OS), DOS) EXEC_SUFFIX := .exe -CPPFLAGS += -I../libgetopt +CPPFLAGS += -I$(DOSLIBS_BASE)/libgetopt # DJGPP has odd uint*_t definitions which cause lots of format string warnings. CFLAGS += -Wno-format # FIXME Check if we can achieve the same effect with -L../libgetopt -lgetopt -LIBS += ../libgetopt/libgetopt.a +LIBS += -lgetopt +LDFLAGS += -L$(DOSLIBS_BASE)/libgetopt/ # Bus Pirate, Serprog and PonyProg are not supported under DOS (missing serial support). ifeq ($(CONFIG_BUSPIRATE_SPI), yes) UNSUPPORTED_FEATURES += CONFIG_BUSPIRATE_SPI=yes @@ -621,9 +623,9 @@ PCILIBS += -lpciutils -lpci PCILIBS += -l$(shell uname -p) else ifeq ($(TARGET_OS), DOS) -# FIXME There needs to be a better way to do this -CPPFLAGS += -I../libpci/include -PCILIBS += ../libpci/lib/libpci.a +CPPFLAGS += -I$(DOSLIBS_BASE)/libpci/include +LDFLAGS += -L$(DOSLIBS_BASE)/libpci/lib/ +PCILIBS += -lpci else PCILIBS += -lpci ifeq ($(TARGET_OS), OpenBSD) diff --git a/README b/README index 2441089..ba7e295 100644 --- a/README +++ b/README @@ -103,20 +103,24 @@ To cross-compile on Linux for DOS: djcrx-2.04pre_20090725-13ap.i386.rpm The cross toolchain packages for your distribution may have slightly different names (look for packages named *djgpp*). - Download pciutils 3.1.5 and apply http://assembler.cz/flashrom/pciutils.patch - Download and compile http://assembler.cz/flashrom/libgetopt/ + + You will need the following library source trees containing their compiled + static libraries either in the parent directory of the flashrom source or + specify the base folder on compile time with the DOSLIBS_BASE parameter. + The default as described above is equal to calling + 'make djgpp-dos DOSLIBS_BASE=..' + + To get and build said libraries... + Download pciutils 3.1.5 and apply http://flashrom.org/File:Pciutils.patch.gz Compile pciutils, see README.DJGPP for instructions. + Download and compile http://flashrom.org/File:Libgetopt.tar.gz Enter the flashrom directory. - ../libpci should contain pciutils source and binaries. - ../libgetopt should contain getopt.a from libgetopt. Run either (change settings where appropriate) make CC=i586-pc-msdosdjgpp-gcc STRIP=i586-pc-msdosdjgpp-strip or (above settings hardcoded) make djgpp-dos - You might have to add WARNERROR=no to the make command line. - To run flashrom.exe, download and unpack - http://homer.rice.edu/~sandmann/cwsdpmi/csdpmi7b.zip and make sure - CWSDPMI.EXE is in the current directory. + To run flashrom.exe, download and unpack http://flashrom.org/File:Csdpmi7b.zip + and make sure CWSDPMI.EXE is in the current directory. To cross-compile on Linux for Windows: -- Kind regards, Stefan Tauner

1 0

Re: [flashrom] Support for intel card eeproms
by Stefan Tauner 05 Sep '13

05 Sep '13

On Wed, 4 Sep 2013 18:47:19 +0200 Ricardo Ribalda Delgado <ricardo.ribalda(a)gmail.com> wrote: > Hello > > We are building a set of cameras with intel 82580 Gigabit chipset. > > Instead of using the intel eeupdate tool to init the card and the mac I > plan to use flashrom. > > The eeprom is accessed with something similar to spi, but AFAIK it does not > follow the jedec standard. > > To probe it, there are some bits on the network card that I can use, that > will tell me if the chip is there and the size. > > I havent digged too much into the code, but I believe that I have to make a > new chip and a new programmer. > > Before starting the work I would like to know if there is something similar > on flashrom that I can use as a example, and if you are interested on such > a patch. There is 0 code for EEPROMs in flashrom yet and we do not plan to work actively on supporting them, but for your approach adding two files, one for the programmer and one for the chip might be a good start :) In the past support for single chips or chip families converged into files with generic functions that support a wide range of different manufacturers, so there is probably no exact template for what you need to do regarding the chip, but that shouldnt be a big issue, just implement the needed functions in a new file, hook it up in chipdrivers.h and add a new entry to flashchips.c. The programmer code will be harder to get right without understanding flashrom's architecture, but maybe you can use Carl-Daniel's script or at least be inspired by it: http://patchwork.coreboot.org/patch/3836/ Alternatively you could take one of the two existing intel nic drivers and just change it where needed. That would not lead to a mergeable patch but might be easier for you (OTOH you would miss to see some implementation details of a new programmer that are under the hood, for example where it needs to be hooked up). I am not sure if we would merge an EEPROM driver anyway, so getting something that works for you should be priority. There might be pre-existing alternatives for what you want... the Intel cards are very widespread and eeupdate is a PITA AFAIK, but I have never looked for a linux application to replace eeupdate... HTH for now. I am looking forward to see any results. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

Support for intel card eeproms
by Ricardo Ribalda Delgado 04 Sep '13

04 Sep '13

Hello We are building a set of cameras with intel 82580 Gigabit chipset. Instead of using the intel eeupdate tool to init the card and the mac I plan to use flashrom. The eeprom is accessed with something similar to spi, but AFAIK it does not follow the jedec standard. To probe it, there are some bits on the network card that I can use, that will tell me if the chip is there and the size. I havent digged too much into the code, but I believe that I have to make a new chip and a new programmer. Before starting the work I would like to know if there is something similar on flashrom that I can use as a example, and if you are interested on such a patch. Thanks! -- Ricardo Ribalda

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom September 2013