Hacker News new | past | comments | ask | show | jobs | submit | saidinesh5's comments login

Usually the bootloader can load a rom using tftp:

https://openwrt.org/docs/guide-user/installation/generic.fla...

You don't need anything except a lan cable. You need to set a static IP to the tftp server machine and name the flashing file properly and it should just work.


Interesting. I did have a working OpenWRT setup initially. I don't recall touching the bootloaders at all and I'm not aware whether they've been set up for the tftp fallback. I'll look into it. Thanks!

Is there any reason why most TVs still don't support USB C display port and just support HDMI?

With the recent drama around HDMI vs. Foss drivers on Linux, I'm curious why haven't we seen that bigger push from TV vendors to support USB C display port.

Most of my monitors work with USB C, Even consoles like steam deck, a lot of high end phones seem to support USB C.

So... Are there any features of HDMI that USB C display port doesn't support?


DisplayPort in native mode lacks some HDMI features such as Consumer Electronics Control (CEC) commands. The CEC bus allows linking multiple sources with a single display and controlling any of these devices from any remote. DisplayPort 1.3 added the possibility of transmitting CEC commands over the AUX channel. From its very first version HDMI features CEC to support connecting multiple sources to a single display as is typical for a TV screen.

The other way round, DisplayPort's Multi-Stream Transport allows connecting multiple displays to a single computer source.

This reflects the facts that HDMI originated from consumer electronics companies whereas DisplayPort is owned by VESA which started as an organization for computer standards.


> From its very first version HDMI features CEC

That depends on whether or not you consider single-link DVI-D as the "very first version" of HDMI.


DP has a different management interface that's actually better because it's a standard unlike CEC.

I imagine CEC could be added to DisplayPort.

DisplayPort->HDMI was the only way I could get my PC to control the TV it was attached to over CEC, since (apparently) the CEC pins aren't enabled on most consumer GPUs, but the DisplayPort aux pin can be used as an alternative.

So the linux DisplayPort driver at least supports the feature, whether or not it's fully standardized/required.


I don't know how true it is, but I heard that

- TV manufacturers are often (always?) members of the HDMI consortium, meaning they financially profit from each device that has an HDMI port.

- Manufacturers of devices with HDMI ports are heavily discouraged from also including competing ports like DP.


DRM is pretty much mandatory in HDMI in home entertainment setup, and is controlled by the media companies' cabal, which is important to vendors in that space (who are often members too).

Also, lowest common denominator HDMI in TV format has HDCP decoder as the only complex part, you can theoretically drive a dumb panel with few fixed function ICs that aren't even related to HDMI. Simplest dumbest case you can advertise the bare minimum supported display setting in EDID, and plop few buffers and ADCs and drive an analog TV off it.

Meanwhile simplest possible DisplayPort implementations still requires that your display can handle packetized data sent over PCI-E PHY layer, with more complex data structures and setup information than "plop an I2C rom chip here, few ADCs and buffer logic here, and you've got HDMI without HDCP to analog CRT".


The world doesn't care about FOSS drivers.

Anyway, HDMI is for TVs and DisplayPort is for monitors. They're both entrenched enough that it doesn't make much sense to try to cross over.


Ok, but, why not just try to converge on one connector? as you say, the world doesn't care...

Fundamentally different goals.

HDMI world wants DRM because other than Kim Dotcom (who is highly problematic for other reasons) no one has dared to stand up to the MAFIAA goons.

Computing world wants DisplayPort and a hassle-free, high quality experience. DRM breaks that.


The manufacturers very much care - every HDMI port (physical or virtual) involves tithe to the HDMI consortium, whereas DisplayPort does not.

I don't follow - surely if the manufacturers have to pay for every port, they'd like something that isn't costing them money?

Which is why in my experience on computer hw it's common to see one, maybe two HDMI (among other reasons, to support things like connecting a console to your monitor), and multiple display port connectors - sometimes it goes ridiculous - a maximalist approach to counting on my laptop, as currently docked, from the point of "ports implemented in GPU" if not actually available physically... gives me one HDMI and 15 DisplayPort, with the HDMI being routable onto a bunch of options. Of course that's a silly comparison, but depending on how licensing is worded I would be really unsurprised if computer manufacturers optimized for lower HDMI port count.

Also, since older HDMI was physically compatible with DVI ports, a lot of computers preferred to keep DVI ports...


>why most TVs still don't support USB C display port and just support HDMI

Cost. USB c has much more overhead. For example, people expect they’ll be able to charge with it and have usb pass through.


>Is there any reason why most TVs still don't support USB C display port and just support HDMI?

Personally I’m convinced it’s mostly because the display manufacturers want to discourage the use of TVs as monitors, in order to protect their margins on monitors.

8k monitors should be sub 1000 usd by now and standard for anyone working with screens. You can get that as a tv but not as a monitor. :(


CEC is probably one of them, but I'm not sure that's a bad thing.

I don't think DisplayPort has an equivalent to eARC either.

> internet really doesn't care about being completely peer-to-peer.

I think this is mostly the way it is because of all the NAT headaches that come with IPv4.

We regularly see the limitations of Dropbox/Google drive when we just want to share that large birthday video with our friends/family. Imagine them having a secure link to your device that you can revoke any time.

Same with all the home automation / iot devices / cctv cameras that have no excuse not to be local first/need you to install an ad infested app.


WebOS/Lune OS recently made a release in February no? Apparently they rebased themselves on top of LG's WebOS OSE. Rebase - being loosely used.

I think the Librem 5's adaptation of Gnome looks like a decent touch friendly Linux OS these days. Haven't touched it in a while though.


I think he's talking about how they(?) market it as open alternative to Android but most of the UI and apps were proprietary.

Some people also don't like it that they had some deal with the Russian Government.


If BSDobelix had done some basic research, this would have turned up:

"In 2024, to escape Russia's investors due to the Ukrainian war, the Jolla initial company filed for bankruptcy, continuing its activity under the JollyBoys name." (https://en.wikipedia.org/wiki/Jolla)

Quite a gutsy move, in my opinion, and as far away from "near scam" as can be.


I have nothing written about Russia nor Ukraine, but closed source software and the promised "pre-order" jolla tablet.

However it's interesting that a Finnish company files bankruptcy and had that much investors from Russia, so thanks for a additional point....and that name JollyBoy...


See https://jolla.com/content/uploads/2023/11/Former_leadership_...

AFAIK russian military uses the devices during the war and moreover, they are designed and approved by the russian government. I saw a few devices from https://auroraos.ru/ . https://www.tadviser.ru/index.php/%D0%9F%D1%80%D0%BE%D0%B4%D... - here is more history



OK, I misunderstood - apologies! You're right about the tablet; I'd forgotten about that...


Kinda of a slow move. The war's second phase started in 2022.


Tbh N9 is still way ahead than today's Android experience imo.

It's also more consistent gestures experience than sailfish. Here you know the gestures are basically for "window/app management". Everything else - they look like regular Android apps.


The basics of making phone calls, texting etc .. all work well on most of the devices - official/community supported.

Older one plus devices, Motorola devices. The guy who ports to some Motorola phones simply doesn't give up and keeps maintaining his ports up to date.

Here's the status of various devices:

https://wiki.merproject.org/wiki/Adaptations/libhybris


Are you saying that Plasma Mobile runs on any device that is supported by libhybris?

I was asking about Plasma Mobile ( https://plasma-mobile.org/get/ ) that the parent mentioned switching to and I wasn't aware that libhybris is a requirement.


If you want a plasma mobile device, your best option is to find devices that are supported by PostmarketOS. That is a distro (kind of like Ubuntu etc ...), which under the hood can use libhybris to talk to Android drivers etc..

https://wiki.postmarketos.org/wiki/Devices

There maintainers create configurations for those specific devices to make them work well with postmarket OS:

https://gitlab.com/postmarketOS/pmaports/-/blob/master/devic...


Honestly the N9/N950 feels a lot more polished - UI wise - than sailfish.

It is kind of expected, given the budget of Nokia ... But even some of the design and aesthetic choices of Sailfish don't really age well once the novelty wears off


Usually the first party supported Sony xperia devices should all work well with all the bells and whistles of sailfish (their Android app support, some proprietary sync functionality)

If you have an old Motorola, OnePlus, older Xiaomi Devices - you can get the community ported Sailfish OS. That won't have their Android app support, but there are other options to get that working.


What are the other options to get Android app support?


There's waydroid:

https://github.com/sailfishos-open/waydroid

There were also rpms of Alien Dalvik (the official Android app runner on paid Sailfish devices) that you can install. But that's kind of piracy.


So they are using waydroid... nice! Use this myself a lot on Linux-based tablets/computers, like the Legion GO.

Wonder how well this integrates with the (edit: Sailfish) OS. Unfortunately, this also does not do screenlocks and therefore has security restrictions and certain apps refuse to work properly.


The good thing is waydroid is fully open source. So you can add OS integrations yourself too. It's not too difficult imo.


I get your point: "patches are welcome", but I meant to understand what it does with Sailfish besides launching applications. Android and MeeGo had the idea of intents, like sending a file through a certain application. Also, the filesystems are probably separated.


Filesystems are separated but i used to bind mount Folders like Documents, Downloads, Pictures etc.. into the Android container.. thereby sharing the important data.

Other integrations could include making sure your contacts between Android and Sailfish are in sync.

Not sure what the status of notifications is.

Keeping the clipboards in sync.

Half of these things can be "hacked into" by using something like kde connect in the waydroid container.

Integration with Android intents like share etc .. would be stretching it..

It'd still be nice to do it properly.


Swapping out is possible only if there are shared libraries though.

For statically linked programs is there anything that can be done?


Valve does a lot of hacks in Proton to make particular games run better. I think swapping a static library might also be possible if you target a particular game.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: