beep code manager for openbmc

[Milton Miller II]

Ren, Zhikuui wrote:
>Patrick Williams wrote:>>On Thu, Sep 02, 2021 at 08:15:21PM +0000, Ren, Zhikui wrote:
>>> Hi All,
>>>
>>> Beepcode manager is a stand-alone beep code service should be
>created to
>>manage the beeper hardware, and provide D-Bus methods to expose the
>>beeper function globally, all other services can use the beeper
>hardware by
>>calling the beep methods.
>>>
>>> This package has been included in our distribution. Now we would
>like  to
>>upstream it and make it available to the community.
>>>
>>>
>>> Since it is now a very light service that only have one source
>file and a service
>>file. I am wondering whether this service can go to an existing
>repository.
>>> If not, we would like to request a new repository for it.
>>>

My thought is perhaps with our progress code logging and 7-segment 
post code display in phosphor-host-postd ?

I could see several of the events mentioned be triggered by writing 
a post code, and there are already a few separate programs in that 
repository, one to record codes and one to display on some 7-segment 
led hardware.  The phosphor-post-code-manager which records the 
history is in its own repository (before the desire to combine them).

I'm certianally open to other suggestions just thought I'd plant a 
seed for discussion.

>>> Thanks,>>> Zhikui
>>>

[various other discussions on interfaces , making the beep codes 
configurable , etc]

>[Ren, Zhikui] To summarize, I think the following steps can be taken:>1. Find an existing home or create a new one for Beep code manager
>2. Upstream existing code as initial check in
>3. create phosphor-dbus-interfaces for it 
>4. update to use phosphor-dbus-interface
>5. further improvements including the two discussed above
>
>Any comments/feedback? 
>
>Thanks,
>Zhikui

milton