3 ms·

> Mostly I'd love to know exactly what this chip/system does, so if anyone here with far more advanced hardware knowledge than any of us have feels up to hackin

by mbell 14y ago

> Mostly I'd love to know exactly what this chip/system does, so if anyone here with far more advanced hardware knowledge than any of us have feels up to hacking around, that'd be amazing! :) Its converting an encoded steam to HDMI output. There aren't enough pins on a lightning connector to directly output HDMI and even if it could, you still need a transceiver somewhere (not particularly trivial in terms of space or power to stuff in the phone). The SoC is most likely a little ARM core to manage stuff (Cortex-M0/3) with a video decoder and HDMI transceiver, the 256MB of ram is there primarily for the decoder to use. It also needs to mux the audio stream into the HDMI encoding. As for 'it runs iOS', your really splitting hairs, its pretty normal for the master devise to load a slave device with its firmware when plugged in (rather than storing the firmware in flash on the slave). The fact that they would use some knocked down version of iOS isn't terribly surprising. Embedded versions of more powerful OSs are used all the time; There is a non-zero chance your stove and microwave are 'running linux'.

vvhn 14y ago
> There is a non-zero chance your stove and microwave are 'running linux'. Unless Linux comes with a BSD license, there is, in fact, zero chance. Apple is known to run a NetBSD variant on the airport routers - I'd say that is what is likely or whatever the hell a "stub version of iOS" means.
- sblom 14y ago
  What does BSD vs GPL have to do with my stove or microwave?
  - dublinben 14y ago
    The GPL requires that any changes (made to code used in released products) be released under the GPL. I'm unaware of any home appliance manufacturer that freely releases the OS of their products under the GPL, as they would have to if they were using Linux.
    - loumf 14y ago
      If they did, they would probably do it the way Amazon does with Kindle or Samsung does with Android. A giant tarball you can download from somewhere on their site, but not necessarily easy to just know about (like a link on the homepage). If you go here: http://opensource.samsung.com http://opensource.samsung.com you can see that they have the OS for some TV's. This is the typical way they comply (with unuseful, unannotated giant dumps). LG actually has some appliances: http://www.lg.com/global/support/opensource/index http://www.lg.com/global/support/opensource/index
  - bobdvb 14y ago
    There is a false assumption that manufacturers don't use Linux because of GPL. Most products don't use Linux because they don't need it, and they use something like FreeRTOS or another commerical RTOS. Plenty of companies use Linux in all sorts of home appliances, mostly TV products, but an increasing number of fridges from companies like Samsung do have Linux and they do release the code. What manufacturers don't do is release the applications that they run on the OS (despite the false assumption that they should).
  - vvhn 14y ago
    I'm sorry, that was a brainfart- I thought you meant the connector and the host device and not quite literally a random microwave and oven :)
kalleboo 14y ago
> There aren't enough pins on a lightning connector to directly output HDMI and even if it could, you still need a transceiver somewhere (not particularly trivial in terms of space or power to stuff in the phone). MicroUSB+MHL accomplishes the same thing quite well on the current crop of Android phones. Why Apple chose the method they did is still quite odd.
- mbell 14y ago
  MHL is an option but it only fixes the number of pins issue. It has the same problem as HDMI out: you need a transceiver capable of multi-Gbit data rates. You also have to get the video output to the transceiver. Its not the easiest thing to do inside a phone, its really not the easiest thing to do when your next phone release is focused on 'thinner and lighter'. Apple already made a strong commitment to AirPlay, so they already had a focus on building a fast, smooth, low power encoder that could encode the entire screen. Once encoded, the stream is probably only a few Mbit/s, a data rate that can easily be transmitted with single ended protocols like SPI. Almost all SoCs already have multiple SPI buses so no need to change any hardware. Their solution may seem inelegant to some, but I think it is great. They managed to support a feature with almost zero hardware costs on the core device (depending on how you assign the lightning connector). A feature that I'm willing to bet only a very small % of all users will ever use. That is a big win, not having to dump extra hardware into a device that only 5% of all users will ever activate does great things for your margin and design flexibility.

by mbell 14y ago

vvhn 14y ago

> There is a non-zero chance your stove and microwave are 'running linux'. Unless Linux comes with a BSD license, there is, in fact, zero chance. Apple is known to run a NetBSD variant on the airport routers - I'd say that is what is likely or whatever the hell a "stub version of iOS" means.

sblom 14y ago
What does BSD vs GPL have to do with my stove or microwave?
- dublinben 14y ago
  The GPL requires that any changes (made to code used in released products) be released under the GPL. I'm unaware of any home appliance manufacturer that freely releases the OS of their products under the GPL, as they would have to if they were using Linux.
  - loumf 14y ago
    If they did, they would probably do it the way Amazon does with Kindle or Samsung does with Android. A giant tarball you can download from somewhere on their site, but not necessarily easy to just know about (like a link on the homepage). If you go here: http://opensource.samsung.com http://opensource.samsung.com you can see that they have the OS for some TV's. This is the typical way they comply (with unuseful, unannotated giant dumps). LG actually has some appliances: http://www.lg.com/global/support/opensource/index http://www.lg.com/global/support/opensource/index
- bobdvb 14y ago
  There is a false assumption that manufacturers don't use Linux because of GPL. Most products don't use Linux because they don't need it, and they use something like FreeRTOS or another commerical RTOS. Plenty of companies use Linux in all sorts of home appliances, mostly TV products, but an increasing number of fridges from companies like Samsung do have Linux and they do release the code. What manufacturers don't do is release the applications that they run on the OS (despite the false assumption that they should).
- vvhn 14y ago
  I'm sorry, that was a brainfart- I thought you meant the connector and the host device and not quite literally a random microwave and oven :)

kalleboo 14y ago

> There aren't enough pins on a lightning connector to directly output HDMI and even if it could, you still need a transceiver somewhere (not particularly trivial in terms of space or power to stuff in the phone). MicroUSB+MHL accomplishes the same thing quite well on the current crop of Android phones. Why Apple chose the method they did is still quite odd.

mbell 14y ago
MHL is an option but it only fixes the number of pins issue. It has the same problem as HDMI out: you need a transceiver capable of multi-Gbit data rates. You also have to get the video output to the transceiver. Its not the easiest thing to do inside a phone, its really not the easiest thing to do when your next phone release is focused on 'thinner and lighter'. Apple already made a strong commitment to AirPlay, so they already had a focus on building a fast, smooth, low power encoder that could encode the entire screen. Once encoded, the stream is probably only a few Mbit/s, a data rate that can easily be transmitted with single ended protocols like SPI. Almost all SoCs already have multiple SPI buses so no need to change any hardware. Their solution may seem inelegant to some, but I think it is great. They managed to support a feature with almost zero hardware costs on the core device (depending on how you assign the lightning connector). A feature that I'm willing to bet only a very small % of all users will ever use. That is a big win, not having to dump extra hardware into a device that only 5% of all users will ever activate does great things for your margin and design flexibility.