Modify

Opened 12 years ago

Last modified 2 years ago

#103 new enhancement

Versioning of Camera Firmwares

Reported by: Suren A. Chilingaryan Owned by: Michele Caselle
Priority: critical Milestone:
Component: UFO Camera Version:
Keywords: Cc: Matthias Balzer, Suren A. Chilingaryan, Andreas Kopmann, Michele Caselle, Uros Stevanovic, Matthias Vogelgesang

Description (last modified by Suren A. Chilingaryan)

I think we need some structuring with versioning of UFO Camera firmwares. I think it would be helpful for the project if I and Matthias (and possibly others) will be able to document in ticketing system all the problems we have experienced working with camera. Unfortunately, at the moment there is no way to distinguish between camera revisions. Only Michele may tell which revision was installed and if there was any changes between today and yesterday. This makes such tracking almost impossible.

I think we need:

  • The current revision to be reported by UFO Camera
  • Firmware for all used revisions to be published at Trac under revision numbers.
  • The recommended version should be highlighted.
  • It would be also good to have the firmware sources to be pushed into our version control system.

Attachments (0)

Change History (11)

comment:1 Changed 12 years ago by Suren A. Chilingaryan

Cc: Matthias Balzer added

comment:2 Changed 12 years ago by Matthias Balzer

Description: modified (diff)
ticket_due: 30/08/2012

comment:3 Changed 12 years ago by Suren A. Chilingaryan

Description: modified (diff)

Matthias B.: you are right. Version control system is in this ticket, too. But I wanted to emphasis this subtopic. Now I put a date in the ticket. I want to have a schedule for these actions. Pleas set as "accept" if you have read this ticket update.

comment:4 Changed 12 years ago by Suren A. Chilingaryan

Michele:

Dear all,

my holidays is almost at the end, and I am almost confused why this have a high priority.
Can we waiting until I will back at KIT?
Moreover, the firmware can not go far from my computer.

Take into account that any new application where the fast PCIe infrastructure could be employed I wish to have at least a control on this, please do not forget to respect the work of the people.

comment:5 Changed 12 years ago by Suren A. Chilingaryan

Michele, I'm completely sure nobody plans to use PCIe infrastructure for other projects without your approval. My proposal is only intended to make our developments more transparent.

Since more people started to use ticketing system in Trac, I want to put the hardware related issues inside. We have some long standing occurring sporadically. For example, data flooding when DMA engine continuously sending data. With tickets we will be able to document each occurrence of the problem providing as much details as possible and helping you
to track the problem down (just see for example how I tracked the problem with hanging of UFO server in ticket 63). However, currently it is impossible to describe in which circumstances the problem occurs. I can only tell it is UFO4 or UFO5, but you have hundreds of revisions. I think it will be much easier if we could specify the revision while explaining the issue in the ticket.

It also would be nice to have associated sources. Nobody will use them without your approval. But see, when I'm on holidays you always can ask Matthias about the software. He will check the sources for a problem and even modify if required. But currently if you are away, Uros just doesn't know which version is inside and if I want to get some information he does not know where to look. If you afraid that other people may misuse your code, I may just restrict access to the sources only to people we agree beforehand. But it would be nice if at least Uros had access.

comment:6 Changed 9 years ago by Suren A. Chilingaryan

I was promised the following.

  • DMA version in register 0x18
  • Application version in register 0x9200

comment:7 Changed 2 years ago by pgslot

pgslot เกมออนไลน์ <a href="https://pg-slot.game/">pg</a> อันดับ 1 ทางเข้าร่วมสนุก PG SLOT แตกง่ายที่สุด เกม พีจี แตกบ่อย แจกของรางวัล ฟรีพอยท์ PG SLOT GAME รางวัลฟรีทุกวัน พร้อมให้บริการ 24 ชั่วโมง

comment:8 Changed 2 years ago by anonymous

pgslot เกมออนไลน์ <a href="https://pg-slot.game/">pgslot</a> อันดับ 1 ทางเข้าร่วมสนุก PG SLOT แตกง่ายที่สุด เกม พีจี แตกบ่อย แจกของรางวัล ฟรีพอยท์ PG SLOT GAME รางวัลฟรีทุกวัน พร้อมให้บริการ 24 ชั่วโมง

comment:9 Changed 2 years ago by anonymous

pgslot เกมออนไลน์https://pg-slot.game/อันดับ 1 ทางเข้าร่วมสนุก PG SLOT แตกง่ายที่สุด เกม พีจี แตกบ่อย แจกของรางวัล ฟรีพอยท์ PG SLOT GAME รางวัลฟรีทุกวัน พร้อมให้บริการ 24 ชั่วโมง

comment:10 Changed 2 years ago by anonymous

pgslot เกมออนไลน์ https://pg-slot.game/ อันดับ 1 ทางเข้าร่วมสนุก PG SLOT แตกง่ายที่สุด เกม พีจี แตกบ่อย แจกของรางวัล ฟรีพอยท์ PG SLOT GAME รางวัลฟรีทุกวัน พร้อมให้บริการ 24 ชั่วโมง

comment:11 Changed 2 years ago by anonymous

pgslot เกมออนไลน์[ https://pg-slot.game/] อันดับ 1 ทางเข้าร่วมสนุก PG SLOT แตกง่ายที่สุด เกม พีจี แตกบ่อย แจกของรางวัล ฟรีพอยท์ PG SLOT GAME รางวัลฟรีทุกวัน พร้อมให้บริการ 24 ชั่วโมง

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The owner will remain Michele Caselle.
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from Michele Caselle to the specified user. Next status will be 'new'.
The owner will be changed from Michele Caselle to anonymous. Next status will be 'assigned'.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.