<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 14, 2015 at 2:11 PM, Paul Menzel <span dir="ltr"><<a href="mailto:paulepanter@users.sourceforge.net" target="_blank">paulepanter@users.sourceforge.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Dear coreboot folks,<br>
<br>
<br>
looking at change set #8214 [1], it adds a comment with a reference to<br>
the Chromium bug tracker at <<a href="http://code.google.com" target="_blank">code.google.com</a>>.<br>
<br>
<a href="http://crosbug.com/p/29117" target="_blank">http://crosbug.com/p/29117</a><br>
<br>
Unfortunately access to view that is denied to me.<br></blockquote><div><br></div><div>We use two issue trackers, one which is public (which <a href="http://crosbug.com" target="_blank">crosbug.com</a> redirects to) and one which is private. The public tracker is used by default for most cases, unless it's known that the subject matter will involve confidential details. The particular issue you cited was likely public to begin with, but later moved or restricted. Restrictions to issues filed on the public tracker are sometimes added if resolving a bug involves discussing confidential details about a chip or product (often in the form of logs / debug output).</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
Looking at some of the items already in the upstream tree, most of them<br>
seem to be accessible though.<br>
<br>
$ git grep crosbug<br>
payloads/libpayload/drivers/serial/ipq806x.c: * See<br>
<a href="http://crosbug.com/p/29313" target="_blank">http://crosbug.com/p/29313</a><br>
payloads/libpayload/drivers/timer/ipq806x.c: *<br>
<a href="http://crosbug.com/p/28880" target="_blank">http://crosbug.com/p/28880</a> for details.<br>
src/ec/google/chromeec/acpi/battery.asl: // a bug in the<br>
Linux kernel: <a href="http://crosbug.com/28747" target="_blank">http://crosbug.com/28747</a><br>
src/ec/google/chromeec/ec_commands.h: *<br>
TODO(<a href="http://crosbug.com/p/11223" target="_blank">crosbug.com/p/11223</a>): This is effectively useless; protocol<br>
is<br>
src/ec/google/chromeec/ec_commands.h: *<br>
TODO(<a href="http://crosbug.com/p/23570" target="_blank">crosbug.com/p/23570</a>): These commands are deprecated, and<br>
will be<br>
src/ec/google/chromeec/ec_commands.h: *<br>
TODO(<a href="http://crosbug.com/p/23747" target="_blank">crosbug.com/p/23747</a>): This is a confusing name, since it<br>
doesn't<br>
src/mainboard/samsung/lumpy/acpi_tables.c: * Provide<br>
option to enable for <a href="http://crosbug.com/p/7925" target="_blank">http://crosbug.com/p/7925</a><br>
src/soc/intel/broadwell/acpi/gpio.asl: // Disabled due<br>
to IRQ storm: <a href="http://crosbug.com/p/29548" target="_blank">http://crosbug.com/p/29548</a><br>
src/vendorcode/google/chromeos/vboot.c: * <a href="http://crosbug.com/17017" target="_blank">crosbug.com/17017</a> */<br>
<br>
So my question is, is access granted to all these bugs eventually?<br></blockquote><div><br></div><div>Issues which are closed now will almost certainly remain that way.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
<br>
Thanks,<br>
<br>
Paul<br>
<br>
<br>
[1] <a href="http://review.coreboot.org/#/c/8214/1/src/mainboard/google/samus/romstage.c" target="_blank">http://review.coreboot.org/#/c/8214/1/src/mainboard/google/samus/romstage.c</a><br>
<br>--<br>
coreboot mailing list: <a href="mailto:coreboot@coreboot.org" target="_blank">coreboot@coreboot.org</a><br>
<a href="http://www.coreboot.org/mailman/listinfo/coreboot" target="_blank">http://www.coreboot.org/mailman/listinfo/coreboot</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div>David Hendricks (dhendrix)<br>Systems Software Engineer, Google Inc.</div>
</div></div>