On 05/08/2026 21:12, Leander Kieweg wrote: >> openrisc is arch. >> opencores is entire org. Are you saying that "Glanda" is this one: >> https://www.glanda.com.au/ >> and opencores releases entire SoCs, thus they integrate their own IPs >> there into final product. I agree though, that opencores should not >> define standalone generic compatibles. > > Fair, those precedents don't really hold up then. > > No relation to glanda.com.au, I wasn't even aware of that company. > This is just a personal hobby project, not a company or organization. > > Given that, what would you suggest instead? I'm open to using a > board-specific compatible as the primary match as discussed, or > whatever naming scheme you'd consider appropriate for an individual's > hobby project.
I am fine with small projects, till we do not have surge of them because anyone clones some project and vibe-codes new soft-core. Projects run on your personal github, without any organization, do not get their own vendor prefix. Why? Because then you come with another project and want one more prefix... Personal vendor prefix would be fine, but different thing: this repo for your design was created a few months ago, with one contributor and ~70 commits. This means it is very new, without users. What is the benefit of having it in Linux kernel for the community? Who needs this, outside of you? Best regards, Krzysztof
