How to use BeagleBoard issue tracker?

How do you think we should use BeagleBoard issue tracker

http://code.google.com/p/beagleboard/issues/list

?

In a wider sense as "todo list" or "open point list"? Or better limit it to something like a "sw bug tracking system"?

Looking to the current entries there (e.g. "New home page"), it seems to be intended to be used in a general way, as "list open points/questions here we don't want to forget".

I would like to use it this way, too. And not limit it to sw bugs only.

Thinking about it, following "open points" come to my mind we could list there:

* USB EHCI issue on OMAP3 Beagle
http://marc.info/?l=linux-omap&m=120954523810023&w=2

* Beagle flaky if used @ 500MHz
http://www.beagleboard.org/irclogs/index.php?date=2008-04-28#T19:17:47

* Why doesn't serial boot C utility work?
http://groups.google.com/group/beagleboard/browse_thread/thread/80ad3da0eb2aa555/239193f1e932eb3c?lnk=gst&q=OMAP3+boot+ROM+UART+download+utility#239193f1e932eb3c

* What's wrong when serial boot perl utility complains with "TIOCSERGETLSR(21593) ioctl failed: The argument is invalid at ./serial-boot.pl line 374 "?
http://groups.google.com/group/beagleboard/browse_thread/thread/80ad3da0eb2aa555/73d42d3fa29680de?lnk=gst&q=OMAP3+boot+ROM+UART+download+utility#73d42d3fa29680de

* How to use fdisk & mkfs.vfat under Linux to create a bootable SD/MMC card?
http://www.beagleboard.org/irclogs/index.php?date=2008-04-24#T15:20:55

* How to detect if a Beagle Ax sample still needs a fix for "There is an issue where on some boards the 1.8V has excessive noise on it. This is the result of two incorrect parts being installed on the board."?
http://www.beagleboard.org/irclogs/index.php?date=2008-04-28#T19:48:12

Would it be okay to add such stuff to issue tracker? What do you think?

Dirk

I believe using it in the general sense is a great idea. If we get a
bit overwhelmed and issues don't look like they are being closed, then
we'll find a new approach. Your list of issues below would be good to
include.

How do you think we should use BeagleBoard issue tracker

http://code.google.com/p/beagleboard/issues/list

?

In a wider sense as "todo list" or "open point list"? Or better limit
it to something like a "sw bug tracking system"?

Looking to the current entries there (e.g. "New home page"), it seems
to be intended to be used in a general way, as "list open
points/questions here we don't want to forget".

I would like to use it this way, too. And not limit it to sw bugs
only.

Thinking about it, following "open points" come to my mind we could
list there:

* USB EHCI issue on OMAP3 Beagle
http://marc.info/?l=linux-omap&m=120954523810023&w=2

* Beagle flaky if used @ 500MHz
http://www.beagleboard.org/irclogs/index.php?date=2008-04-28#T19:17:47

I believe this has been resolved, but putting it on the issue tracker
would be a nice way of confirming.

Jason Kridner wrote:

I believe using it in the general sense is a great idea. If we get a
bit overwhelmed and issues don't look like they are being closed, then
we'll find a new approach. Your list of issues below would be good to
include.

:slight_smile:

Will do so.

Will additionally add

* Getting JTAG/Flyswatter to work.

Dirk

Jason Kridner wrote:

I believe using it in the general sense is a great idea. If we get a
bit overwhelmed and issues don't look like they are being closed, then
we'll find a new approach. Your list of issues below would be good to
include.

Done:

http://code.google.com/p/beagleboard/issues/list

Please check/correct/add what you like.

Two notes:

* I didn't manage to leave "Owner" field empty. Sorry.

* How to create links in issue description that are directly clickable?

Dirk